-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Make rustc_on_unimplemented
std-agnostic for alloc::rc
#115210
Make rustc_on_unimplemented
std-agnostic for alloc::rc
#115210
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @WaffleLapkin (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you squash the commits together?
@rustbot author |
e1217e6
to
6ec570a
Compare
Squashed |
@rustbot ready |
Thanks! @bors r+ rollup |
…iaskrgr Rollup of 4 pull requests Successful merges: - rust-lang#115197 (Remove special cases that are no longer needed due to rust-lang#112606) - rust-lang#115210 (Make `rustc_on_unimplemented` std-agnostic for `alloc::rc`) - rust-lang#115237 (Fixup sparc-unknown-none-elf table spacing) - rust-lang#115244 (Migrate GUI colors test to original CSS color format) r? `@ghost` `@rustbot` modify labels: rollup
Revert "Suggest using `Arc` on `!Send`/`!Sync` types" Closes rust-lang#114687. This is a clean revert of rust-lang#88936 + rust-lang#115210. The suggestion to Arc\<{Self}\> when Self does not implement Send is *always* wrong. rust-lang#114842 is considering a way to make a more refined suggestion.
See #112923
Just a few lines related to
alloc:rc
forSend
andSync
.That seems to be all of the
... = "std::..."
issues found, but there a few notes withstd::
inside them still.r? @WaffleLapkin