Add a scheme to find the place where an id was destroyed
cc https://github.com/rust-lang/miri/issues/974
I'm not too happy with it, but since stacked borrows don't have access to the current call stack, I can't just report a warning as per https://github.com/rust-lang/miri/issues/797
We could add some global mutex that we can throw strings at and `step` will clear out that mutex and report warnings before moving the `statement_id` or the `block_id`, not sure how well that would work. For now I think this is sufficient
Updated CI config to reflect deprecation of rustup uninstall
In the same spirit as #1110😄
This PR from the rustup repository brought me here: https://github.com/rust-lang/rustup/issues/2148
TL;DR With rustup 1.21.0 `rustup install` and `rustup uninstall` are being deprecated in favor of `rustup toolchain install` and `rustup toolchain uninstall`. There's plenty of code/documentation out there that needs to be updated to reflect this.
Thought It would be cool to help, however small the change may be. :)
Keep up the great work!
Updated README to reflect deprecation of rustup install
This PR from the rustup repository brought me here: https://github.com/rust-lang/rustup/issues/2148
TL;DR With rustup 1.21.0 `rustup install` and `rustup uninstall` are being deprecated in favor of `rustup toolchain install` and `rustup toolchain uninstall`. There's plenty of code/documentation out there that needs to be updated to reflect this.
Thought It would be cool to help, however small the change may be. :)
Keep up the great work!
better way to ignore tests in Miri
This is better because it avoids warnings due to unused imports (the ignored tests still get compiled, just not executed).
