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
I'm trying to figure out how to create always firing assertions as assert false seems to be disallowed by opts.
assert false
I sometimes tend to write code like this:
when cond $ do comment "this is pretty bad" assert $ not cond
See for example GaloisInc/ivory-tower-stm32@aafc0ca#diff-1651b43e296daea4ab0ba777cb26b769R90
I guess I would prefer to be able to express this as something like fail
fail
when cond $ do fail "how did we get here"
assuming this is taking care of some rare condition like improper hardware configuration.
Looks like this would need another primitive along with assert.
assert
Any thoughts?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm trying to figure out how to create always firing assertions as
assert false
seems to be disallowed by opts.I sometimes tend to write code like this:
See for example GaloisInc/ivory-tower-stm32@aafc0ca#diff-1651b43e296daea4ab0ba777cb26b769R90
I guess I would prefer to be able to express this as something like
fail
assuming this is taking care of some rare condition like improper hardware configuration.
Looks like this would need another primitive along with
assert
.Any thoughts?
The text was updated successfully, but these errors were encountered: