-
Notifications
You must be signed in to change notification settings - Fork 3
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
either alias thereis
to any
or new clause
#60
Comments
In If the inconsistency bothers you, it is probably good to switch from the
I think that it would be overkill. Generally, a non-nil value works as well as If one is relying on a difference between |
It does honestly. I'll make a PR for this. And being able to return something other than t or nil might be useful (if not abused of course).
Thought it might be. Good thing I asked.
True.
That's cool I didn't now this. |
So, any is a good (slightly better in my opinion) name than thereis. I made
thereis
modeling the specification of theiterate
thereis
clause. However, it contrasts fromnever
andalways
in that it actually returns a value. Maybe, to be consistent the behavior withalways
andnever
, anany
clause should strictly return a boolean.I don't know whether this is overkill or not, but I could whip up a PR with
alwaysis
neveris
clauses which contrast with their counterparts in that they return values as opposed to booleans.The text was updated successfully, but these errors were encountered: