You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thread '<unnamed>' panicked at rust_verify/src/verifier.rs:728:21:
internal error: generated ill-typed AIR code: error 'in call to ens%main!owl_unit., expected 2 arguments, found 1 arguments' in expression '(ens%main!owl_unit. 0)'
note: [run with `RUST_BACKTRACE=1` environment variable to display a backtrace](https://play.verus-lang.org/?version=stable&mode=basic&edition=2021#)
thread '<unnamed>' panicked at rust_verify/src/verifier.rs:339:17:
dropped, expected call to `into_inner` instead
stack backtrace:
...
On the other hand, removing the ensures res == () on owl_unit() makes the panic go away (link).
Thanks to parametricity, the ensures res == () spec is not actually needed, but noting in case it points to a bigger bug.
The text was updated successfully, but these errors were encountered:
Chris-Hawblitzel
changed the title
Ensures clause with <return value> == () panics the verifier
Invalid AIR generation when returning unit type
Jun 12, 2024
The following code:
panics the verifier, as follows:
Minimal playground link with full backtrace
On the other hand, removing the
ensures res == ()
onowl_unit()
makes the panic go away (link).Thanks to parametricity, the
ensures res == ()
spec is not actually needed, but noting in case it points to a bigger bug.The text was updated successfully, but these errors were encountered: