Skip to content
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

Should map/bind/then catch the exceptions throw by the continuation? #15

Open
viboes opened this issue May 25, 2014 · 0 comments
Open
Labels

Comments

@viboes
Copy link
Collaborator

viboes commented May 25, 2014

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant