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
Currently, many exceptions thrown by h5cpp can be identified only via inspection of std::runtime_error::what.
h5cpp
std::runtime_error::what
A common base type for all exceptions thrown in response to errors originating from libhdf would allow more fine grained error handling.
libhdf
A further enhancement could be custom exception types for common failure cases, especially those which one can recover from.
The text was updated successfully, but these errors were encountered:
Good point. We need to discuss this. But you made a point here.
Sorry, something went wrong.
Tobias says this is easy to do.
No branches or pull requests
Currently, many exceptions thrown by
h5cpp
can be identified only via inspection ofstd::runtime_error::what
.A common base type for all exceptions thrown in response to errors originating from
libhdf
would allow more fine grained error handling.A further enhancement could be custom exception types for common failure cases, especially those which one can recover from.
The text was updated successfully, but these errors were encountered: