-
Notifications
You must be signed in to change notification settings - Fork 13.4k
'Assertion !cx.terminated failed' involving nested rets #894
New issue
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
Comments
Fixing this will involve either inserting checks with early-return paths after each and every call to trans_expr and trans_lval, or adding some machinery to the builder to simply ignore extra code added to terminated blocks. |
This looks a lot like all of other bottom returning !cx.terminated bugs that tjc was fixing. Is it different in some way? |
bors
pushed a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 26, 2020
Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.10 to 1.0.11. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](dtolnay/thiserror@1.0.10...1.0.11) Signed-off-by: dependabot-preview[bot] <[email protected]>
coastalwhite
pushed a commit
to coastalwhite/rust
that referenced
this issue
Aug 5, 2023
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
* Document and move vtable metadata stuff into a module * Move vtable restrictions linking into cargo-kani * move library/kani_metadata to src/kani_metadata
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Results in an assertion in a function called "Br":
Same error message as in #893, but a very different testcase.
The text was updated successfully, but these errors were encountered: