-
Notifications
You must be signed in to change notification settings - Fork 100
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
Exceptions #48
Comments
👍 to custom exception type if you see a benefit (as long as it inherits from |
A custom exception type would allow a user to differentiate between an exception thrown by our variant type and an exception that is somehow propagated from a type wrapped in the variant. I am not sure this is strictly necessary, but it would be cleaner in any case. |
@joto - sounds good re: custom exception. |
I have create a new class |
closing as this issue moved to #95 |
Currently
std::runtime_exception
is thrown in a few cases. Should we have our own exception type?.In the case of
get<wrong_type>()
P0088R0 usesbad_variant_access
derived fromlogic_error
for this.The text was updated successfully, but these errors were encountered: