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
Probably all the methods should be constexpr
scope_guard
Maybe this should actually be part of the user api instead of hidden?
There's some differences in implementation there (cant remember details without looking at review) - is there something new and valuable there?
The text was updated successfully, but these errors were encountered:
Don't pay, for what you don't use - should the release method be by default in the scope_guard class? Maybe it should be a mixin?
release
Sorry, something went wrong.
scope_fail and scope_success both require to use the header <exception> (for std::uncaught_exceptions()). Should <scope> be reliant on this header?
scope_fail
scope_success
<exception>
std::uncaught_exceptions()
<scope>
Since scope if fundamentally about dealing with exceptions I think that is a requirement.
JeffGarland
No branches or pull requests
constexpr all the things
Probably all the methods should be constexpr
is
scope_guard
exposition only or notMaybe this should actually be part of the user api instead of hidden?
boost divergence
There's some differences in implementation there (cant remember details without looking at review) - is there something new and valuable there?
The text was updated successfully, but these errors were encountered: