-
Notifications
You must be signed in to change notification settings - Fork 13
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
MonadFail
compliance
#49
Comments
Thanks for fixing this! I tested this commit successfully in a project of mine. Can you cut a release to Hackage? I can post a PR to Stackage to re-integrate into LTS. |
Now back in stackage, I think this can be closed. Thank you! |
Indeed. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #48: ginger currently fails to compile on GHC 8.8 due to
MonadFail
.PR #48 suggests widening
Monad
constraints to arbitraryMonadFail
instances, but I think it would be more prudent to integrate error handling into therunXXXX
functions and theRun
monad stack itself (e.g. usingExceptT
), and while we're at it, introduce a saner / more specific error type. We're going to break the API anyway, might as well use this as an opportunity for improvement.The text was updated successfully, but these errors were encountered: