-
Notifications
You must be signed in to change notification settings - Fork 94
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
Use the new Result type instead of Choice for Errors #52
Comments
Indeed.
|
I decided to use this approach when possible, ie for Functors, Applicatives and Monads. But there are other situations where only one should be the default to model computations. See my comment on the commit for a summary of all these changes. I'm happy to discuss further, or eventually re-open this issue and revert that commit. |
No, I think selecting one approach is good. |
We'll need to adjust to what would be the new standard for signaling errors.
The question is what do we do with the existing type
Choice<'OK,'Error>
.I think we should keep if as much as possible for backwards compatibility, but not just between this library version, there might be a lot of source code that uses the Choice convention and needs to keep working without doing a big refactoring.
The text was updated successfully, but these errors were encountered: