-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add Stdlib.Data.Result
and find
in Stdlib.Data.List
#106
Conversation
The formatting check is failing because of: |
Stdlib.Data.Either
and find
in Stdlib.Data.List
Stdlib.Data.Result
and find
in Stdlib.Data.List
As for the |
Thanks for the encouragement, I'll raise an issue. |
This update adds the stdlib Result type and a `find` function to `List`. See anoma/juvix-stdlib#106
This update adds the stdlib Result type and a `find` function to `List`. See anoma/juvix-stdlib#106
This update adds the stdlib Result type and a `find` function to `List`. See anoma/juvix-stdlib#106
This update adds the stdlib Result type and a `find` function to `List`. See anoma/juvix-stdlib#106
This PR adds implementations of the following, with corresponding tests:
Result
type with associated functions to the standard library.find
function toStdlib.Data.List
Requirements for both arose when writing Anoma applications.
NB:
Adding the
{-# specialize: [1] #-}
pragma tofind
causes the compiler to go into an infinite loop when compiling afind
call with predicateconst false
, e.gSo I've omitted that for now and
I'll raise a separate bug, I suspect I was using thespecialize
pragma incorrectly.