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.

Sign up for GitHub

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

Jump to bottom

Are state modifications supposed to be so lazy? #1018

Open
treeowl opened this issue Dec 27, 2022 · 1 comment
Open

Are state modifications supposed to be so lazy? #1018

treeowl opened this issue Dec 27, 2022 · 1 comment

Comments

@treeowl
Copy link
Contributor

treeowl commented Dec 27, 2022

It looks like all the MonadState operations modify the state lazily, using modify rather than modify'. Is this intentional? If so, do we want ones that don't do that? If so, we're likely to get some naming clashes with #1017, whose strict state changers force both the new state and the targets(s) within it.
@treeowl
Copy link
Contributor Author

treeowl commented Dec 27, 2022

Ah, I guess that's to support the lazy state monad transformer, weird as it is. Hmph.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@treeowl