Skip to content
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.

Sign up for GitHub

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

Jump to bottom

MonadError instance for Kleisli #1542

Closed
durban opened this issue Feb 22, 2017 · 1 comment
Closed

MonadError instance for Kleisli #1542

durban opened this issue Feb 22, 2017 · 1 comment

Comments

@durban
Copy link
Contributor

durban commented Feb 22, 2017

Is there any reason for not having a MonadError instance for Kleisli? Since MonadError seems to be simply Monad and ApplicativeError, and Kleisli has instances of both, it seems like it could work. Although prioritizing the instance could be a little tricky, I guess...
@kailuowang
Copy link
Contributor

kailuowang commented Feb 22, 2017 •
edited by peterneyens
Loading

I think we should have a MonadError instance for Kleisli. Prioritizing shouldn't be too tricky. We just need a new layer between the current KleisliInstance and KleisliInstance0 and move ApplicativeError instance there. This probably means that rename all KleisliInstanceN to KleisliInstanceN+1 and name the new layer KleisliInstance0. Care to give a try? :)

@durban durban mentioned this issue Feb 26, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kailuowang @durban