-
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
Replace unsafe_destructor_blind_to_params with may_dangle #62568
Conversation
Or should I remove support for |
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.
Or should I remove support for
#[unsafe_destructor_blind_to_params]
attribute completely?
Yes
#[may_dangle]
is unsafe, so all of the implementations using it need to be unsafe impl
s.
Yup! I completely forgot about that. |
5afcf80
to
c2d96da
Compare
The build is passed. |
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 re-wrap the text in comments that now have a short line?
Therefore we also remove `#[unsafe_destructor_blind_to_params]` attribute completly.
c2d96da
to
6d66fe2
Compare
@@ -641,6 +638,8 @@ declare_features! ( | |||
(removed, extern_in_paths, "1.33.0", Some(55600), None, | |||
Some("subsumed by `::foo::bar` paths")), | |||
(removed, quote, "1.33.0", Some(29601), None, None), | |||
// Allows using `#[unsafe_destructor_blind_to_params]` (RFC 1238). | |||
(removed, dropck_parametricity, "1.38.0", Some(28498), None, None), |
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.
Is this correct? This features is unstable since 1.3.0
.
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.
AFAIK unstable features just disappear entirely, no need to keep any trace of them around.
6d66fe2
to
8347917
Compare
@bors r+ rollup |
📌 Commit 8347917 has been approved by |
…wjasper Replace unsafe_destructor_blind_to_params with may_dangle This PR will completely remove support for `#[unsafe_destructor_blind_to_params]` attribute, which is deprecated in rust-lang#38970 by `[may_dangle]` unsafe attribute. Closes rust-lang#34761
Rollup of 12 pull requests Successful merges: - #61535 (Coherence test when a generic type param has a default value from an associated type) - #62274 (rustc_mir: follow FalseUnwind's real_target edge in qualify_consts.) - #62431 (Add messages to `Option`'s and `Result`'s `must_use` annotation for `is_*`) - #62453 (in which we suggest anonymizing single-use lifetimes in paths ) - #62568 (Replace unsafe_destructor_blind_to_params with may_dangle) - #62578 (Add test for #49919) - #62595 (Document that the crate keyword refers to the project root) - #62599 (move mem::uninitialized deprecation back by 1 release, to 1.39) - #62605 (Emit dropped unemitted errors to aid in ICE debugging) - #62607 (Correctly break out of recovery loop) - #62608 (`async unsafe fn` tests) - #62623 (downgrade indirect_structural_match lint to allow) Failed merges: r? @ghost
This PR will completely remove support for
#[unsafe_destructor_blind_to_params]
attribute,which is deprecated in #38970 by
[may_dangle]
unsafe attribute.Closes #34761