-
Notifications
You must be signed in to change notification settings - Fork 172
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
un-deprecate Lwt_result
#320
Comments
I concur. This is a very useful module which does not have other counter parts in the library ecosystem. |
FWIW, I gave this a +1, but I have to delay making a positive decision on this due to time constraints. Any links for future reading, libraries that do this right (probably Async), in-depth discussion, etc., appreciated. |
Related modules from Async:
|
Did not annotate Lwt_sequence for the time being, as it is still used by the Lwt API. Closes #107.
For those interested, follow-up design issues in #324. |
Thanks! |
@aantron Hello! So what is a replacement for |
@tte this module is not deprecated or experimental since Lwt 2.7.1 (April). It is a supported part of Lwt. |
I still don't really understand why the module was deprecated, but the more I use lwt the more I can't bear with exception-based error handling in it. I think a well-developped, convenient
Lwt_result
module is critical for good error handling. Can we use this issue to discuss the future ofLwt_result
then?The text was updated successfully, but these errors were encountered: