-
Notifications
You must be signed in to change notification settings - Fork 376
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
Move some derivations into coresponding algebras #188
Comments
Ah, I wanted to just ask the same. My confusion was especially about |
The list in this issue is just an outline of derivations we have. if we move them into algebras we should also show default derivation. In case of I have just taken look at bimap and indeed there is no word about
One thing i know is that |
Maybe what we should do is:
|
Currently this are derivations separately from algebras but I think we can move them to algebras:
map
may be derived frombimap
=> BiFunctormap
may be derived frompromap
=> ProFunctormap
may be derived fromtraverse
=> Traversablereduce
may be derived fromtraverse
=> Traversablemap
may be derived fromap
andof
=> Applicativemap
may be derived fromchain
andof
=> Monadap
may be derived fromchain
=> ChainAs discussed in #179 we should at least state that
<*> = ap
in Apply and Chain (or Applicative and Monad) but we should also investigate if other derivations should be moved to corresponding algebras.The text was updated successfully, but these errors were encountered: