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
This wrongly passes mode-checking (it actually fails due to an unrelated erasure error, but this issue isn't about that):
struct Foo { #[spec] a: u64, #[proof] b: u64, } #[proof] fn some_call(#[spec] x: u64, #[proof] y: u64) { } #[proof] fn t() { #[proof] let foo = Foo { a: 5, b: 6 }; #[proof] let Foo { b, a } = foo; some_call(b, a); }
Meanwhile, this wrongly gives an error:
#[proof] fn t() { #[proof] let foo = Foo { a: 5, b: 6 }; #[proof] let Foo { b, a } = foo; some_call(a, b); }
error: expression has mode spec, expected mode proof --> test_pat_destruct.rs:26:18 | 26 | some_call(a, b); | ^
It looks like mode-checking doesn't handle let Foo { b, a } correctly because the order of its fields are wrong.
let Foo { b, a }
The text was updated successfully, but these errors were encountered:
fixed by 9eb7b12
Sorry, something went wrong.
No branches or pull requests
This wrongly passes mode-checking (it actually fails due to an unrelated erasure error, but this issue isn't about that):
Meanwhile, this wrongly gives an error:
It looks like mode-checking doesn't handle
let Foo { b, a }
correctly because the order of its fields are wrong.The text was updated successfully, but these errors were encountered: