-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Std panicking unsafe block in unsafe fn #74200
Std panicking unsafe block in unsafe fn #74200
Conversation
r? @shepmaster (rust_highfive has picked a reviewer for you, use r? to override) |
5fc0e08
to
2292064
Compare
@Mark-Simulacrum the last commit made the |
☔ The latest upstream changes (presumably #73265) made this pull request unmergeable. Please resolve the merge conflicts. |
r=me with a rebase |
12fec55
to
a39aae8
Compare
Rebase done, checks are in progress. 😃 |
Please also squash all commits into one. |
This adds SAFETY comments where necessary, explaining the preconditions and how they are respected.
a39aae8
to
82ccdab
Compare
@bors r=Mark-Simulacrum rollup |
📌 Commit 82ccdab has been approved by |
Rollup of 8 pull requests Successful merges: - rust-lang#74200 (Std panicking unsafe block in unsafe fn) - rust-lang#75286 (Add additional case for Path starts with) - rust-lang#75318 (Resolve `char` as a primitive even if there is a module in scope) - rust-lang#75320 (Detect likely `for foo of bar` JS syntax) - rust-lang#75328 (Cleanup E0749) - rust-lang#75344 (Rename "Important traits" to "Notable traits") - rust-lang#75348 (Move to intra-doc links in library/core/src/time.rs) - rust-lang#75350 (Do not ICE when lowering invalid extern fn with bodies) Failed merges: r? @ghost
Partial fix of #73904.
This encloses
unsafe
operations inunsafe fn
inlibstd/ffi/panicking.rs
.I also made a two lines change to
libstd/thread/local.rs
to add the necessaryunsafe
block without breaking everything else.@rustbot modify labels: F-unsafe-block-in-unsafe-fn