-
Notifications
You must be signed in to change notification settings - Fork 121
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
introduce discardUnless
#374
base: master
Are you sure you want to change the base?
Conversation
What's the use case for this? It's unfortunate that this has a similar name to |
I should clarify. I don't feel particularly strongly about this idea (and the name does suck, perhaps |
I'll clarify some more. The problem raised by the issue is basically that We can have a separate conversation about what the role of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think discardUnless
is a better name
suchThatDiscard
suchThatDiscard
~discardUnless
suchThatDiscard
~discardUnless
discardUnless
I must admit, I'm a bit sceptical that people will actually use this, just because I always find the |
Closes #363
The tricky thing here is the lazy behaviour of
Gen
andforAll
. That's what makes me unsure whether or notsuchThatDiscard
is a good idea in practice.