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
Have you though about adding an ensure! macro as well in the same vein as the one in failure?
ensure!
We use failure today and with quite a bit of ensure! which I find makes quite compact and explicit code, and has a nice naming connection to assert!.
failure
assert!
Would you be open to adding ensure! to this crate?
The text was updated successfully, but these errors were encountered:
Thanks @repi, good call. I would accept a PR to add an ensure macro.
Sorry, something went wrong.
Thanks, I'll look into it.
Add ensure macro.
a1306a2
Fix dtolnay#1.
Successfully merging a pull request may close this issue.
Have you though about adding an
ensure!
macro as well in the same vein as the one in failure?We use
failure
today and with quite a bit ofensure!
which I find makes quite compact and explicit code, and has a nice naming connection toassert!
.Would you be open to adding
ensure!
to this crate?The text was updated successfully, but these errors were encountered: