-
Notifications
You must be signed in to change notification settings - Fork 332
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
Find a way to test MIR code that rustc won't emit #196
Labels
A-tests
Area: affects our test suite or CI
C-enhancement
Category: a PR with an enhancement or an issue tracking an accepted enhancement
Comments
One way you could do this is use valid Rust syntax and have an AST-to-MIR transform (maybe use HIR to get types that you can use |
oli-obk
added
the
C-enhancement
Category: a PR with an enhancement or an issue tracking an accepted enhancement
label
Jun 14, 2017
We now have |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-tests
Area: affects our test suite or CI
C-enhancement
Category: a PR with an enhancement or an issue tracking an accepted enhancement
It would be nice to be able to test miri against known-bad MIR code -- like, code that uses
StorageLive
/StorageDead
incorrectly, just to make sure that miri catches such errors. Some more examples will come come up with the stuff about unsafe code guidelines that I'm working on.It seems that we need something like a MIR parser for this, though?
The text was updated successfully, but these errors were encountered: