We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is easy to catch the exceptions when the type is expected<exception_ptr,T>.
expected<exception_ptr,T>
However, doing it for expected<E,T> needs a conversion from the current exception and the error E.
expected<E,T>
This proposal requires that the continuation doesn’t throw exceptions as we don’t have a general solution.
Should expected<exception_ptr,T>::map/bind/then catch the exceptions and propagate them on the result?
expected<exception_ptr,T>::map/bind/then
Should expected<E,T>::map/bind/then catch the exceptions and propagate them on the result by doing a transformation from the exception to the error?
expected<E,T>::map/bind/then
If yes, how to configure it?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It is easy to catch the exceptions when the type is
expected<exception_ptr,T>
.However, doing it for
expected<E,T>
needs a conversion from the current exception and the error E.This proposal requires that the continuation doesn’t throw exceptions as we don’t have a general solution.
Should
expected<exception_ptr,T>::map/bind/then
catch the exceptions and propagate them on the result?Should
expected<E,T>::map/bind/then
catch the exceptions and propagate them on the result by doing a transformation from the exception to the error?If yes, how to configure it?
The text was updated successfully, but these errors were encountered: