-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Don't run MIR unsafeck at all when using -Zthir-unsafeck
#87527
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Huh 😄 how does it then work that we don't see MIR unsafeck messages with -Zthir-unsafeck? Do we abort compilation before we get there if there are any errors? |
That's because the rust/compiler/rustc_mir/src/transform/check_unsafety.rs Lines 506 to 570 in aea2e44
|
@bors r+ |
📌 Commit 40b57be has been approved by |
…oli-obk Don't run MIR unsafeck at all when using `-Zthir-unsafeck` I don't know how I missed this :D r? `@oli-obk`
Rollup of 10 pull requests Successful merges: - rust-lang#81050 (Stabilize core::task::ready!) - rust-lang#81363 (Remove P: Unpin bound on impl Future for Pin) - rust-lang#86839 (Add doc aliases to fs.rs) - rust-lang#87435 (fix example code for E0617) - rust-lang#87451 (Add support for tuple struct field documentation) - rust-lang#87491 (Integrate context into the memorial to Anna) - rust-lang#87521 (Add long explanation for E0498) - rust-lang#87527 (Don't run MIR unsafeck at all when using `-Zthir-unsafeck`) - rust-lang#87550 (Add `CI_ONLY_WHEN_CHANNEL` and run `x86_64-gnu-stable` only on nightly) - rust-lang#87565 (Use backticks when referring to `core::future::Ready` in panic message) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
I don't know how I missed this :D
r? @oli-obk