-
Notifications
You must be signed in to change notification settings - Fork 706
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
Consistent datatypes in scalaz. #2051
Comments
This was referenced Apr 4, 2019
Closed
TomasMikula
pushed a commit
that referenced
this issue
Apr 8, 2019
GodPlaysChess
added a commit
to GodPlaysChess/scalaz
that referenced
this issue
Apr 9, 2019
GodPlaysChess
added a commit
to GodPlaysChess/scalaz
that referenced
this issue
Apr 9, 2019
GodPlaysChess
added a commit
to GodPlaysChess/scalaz
that referenced
this issue
Apr 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
scalaz introduces better versions of the standard datatypes, such as
==>>
(Map),Maybe
,IList
, but does not use it itself (for instanceMap
api returnsList
instead ofIList
andOption
instead ofMaybe
) , which makes very cumbersome to utilise them.I identified those places:
DataTypes:
Typeclasses:
I discussed it in gitter and going to link corresponding PRs to this issue.
I think it makes sense to change
Foldable
andEnum
typeclass as well. What do you think?The text was updated successfully, but these errors were encountered: