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

io-classes: MonadMaskingState inconvenient #194

Open
dcoutts opened this issue Nov 27, 2024 · 0 comments
Open

io-classes: MonadMaskingState inconvenient #194

dcoutts opened this issue Nov 27, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@dcoutts
Copy link
Contributor

dcoutts commented Nov 27, 2024

It is unclear to me why MonadMaskingState is separate from MonadMask. Is there some good reason?

It is a bit inconvenient, when one is already using MonadMask and then wanting to use one of the other masking-related functions and having to propagate a new class constraint everywhere.

And related: why does MonadEvaluate inherit from MonadThrow? I can't see how they are related.
@dcoutts dcoutts added the enhancement New feature or request label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dcoutts