Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate redundant state management primitives #51

Open
harendra-kumar opened this issue May 10, 2017 · 2 comments
Open

Deprecate redundant state management primitives #51

harendra-kumar opened this issue May 10, 2017 · 2 comments

Comments

@harendra-kumar
Copy link
Contributor

There are two versions of state management primitives, ending with Data and ending with State, it creates unnecessary confusion. It is better to not have redundancy at all, therefore we can deprecate and later remove one set of these. I guess the ones with State suffix should be removed.

@agocorona
Copy link
Collaborator

The problem I detected with the suffix *Data is that haskellers associate it with mutable state. It is not. It is pure state, like in the state monad. I introduced the suffix *State just for this reason.... maybe *Data is to be deprecated. I use *Data trough all the sources...

@harendra-kumar
Copy link
Contributor Author

I suggested to keep "Data" because:

  1. It is the one being used widely
  2. We store and retrieve by data types, so "Data" is sort of a reminder for that.

I think the confusion may be largely because it was not properly explained in the documentation and people made their own guesses how it might behave. I have added concise and precise documentation in the module so that problem will not be there. Though I would be fine with any one of those, as long as we have only one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants