-
Notifications
You must be signed in to change notification settings - Fork 9
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
Why did fromObject change? #30
Comments
Using Why do you say it has nothing to do with monads? For the simplest cases, it requires at least You're arguing for using a specific instance of Why do you feel this is a problem? Are you running into performance issues due to the abstraction? |
Do not change please. It's perfectly fine the way it is now. |
The problem I am experiencing with this change, unless I am missing something fundamental about Haskell, is that it is impossible to handle failure in a generic way. When fromObject returned a
I don't think you can do the equivalent with the new implementation, as failure may have a completely different manifestation depending on the monad? |
I was trying to update some old code which was still using the
msgpack
package, so I tried switching to this fork. I see theMessagePack
class now hasinstead of
Can you explain the rationale for this change? I see no reason why
fromObject
needs to work polymorphically over all monads, it has nothing to do with monads at all! You end up using just thefail
method for all your instances. At best, you could changeMaybe a
toEither Error a
using anError
datatype.The text was updated successfully, but these errors were encountered: