Rename macro SmartPointer to CoercePointee#131284
Conversation
|
@rustbot labels +F-derive_smart_pointer |
| #[unstable(feature = "derive_smart_pointer", issue = "123430")] | ||
| pub macro SmartPointer($item:item) { | ||
| #[unstable(feature = "dervie_coerce_referent", issue = "123430")] | ||
| #[cfg(not(bootstrap))] |
There was a problem hiding this comment.
I will remove this in the next beta release.
There was a problem hiding this comment.
You don't need to remove it; it'll get removed by the release team member doing the beta release.
This comment has been minimized.
This comment has been minimized.
2d31f15 to
ffef110
Compare
This comment has been minimized.
This comment has been minimized.
a761a7b to
b5f8711
Compare
|
@rustbot blocked Blocked on FCP finishing |
| (incomplete, deref_patterns, "1.79.0", Some(87121)), | ||
| /// Allows deriving `SmartPointer` traits | ||
| (unstable, derive_smart_pointer, "1.79.0", Some(123430)), | ||
| /// Allows deriving `CoerceReferent` traits |
There was a problem hiding this comment.
I believe you should register derive_smart_pointer as a removed feature, or perhaps look into how we've handled renamed features in the past.
There was a problem hiding this comment.
Applied. I moved it into the removed list.
|
☔ The latest upstream changes (presumably #131372) made this pull request unmergeable. Please resolve the merge conflicts. |
6e7d624 to
d83b461
Compare
SmartPointer to CoerceReferentSmartPointer to CoercePointee
d83b461 to
ad79281
Compare
|
This is still waiting for the FCP to finish. To avoid additional churn, and since I see no rush here: @rustbot blocked |
|
☔ The latest upstream changes (presumably #131612) made this pull request unmergeable. Please resolve the merge conflicts. |
move derive_smart_pointer into removed set
| /// Allows deriving traits as per `CoercePointee` specification | ||
| (unstable, derive_coerce_pointee, "1.79.0", Some(123430)), |
There was a problem hiding this comment.
Why is this a lang feature at all? The feature gating should be a library feature, since all this gates is a macro, and no behavior in the compiler.
I believe that you can remove this.
| /// Allows deriving traits as per `CoercePointee` specification | ||
| (unstable, derive_coerce_pointee, "1.79.0", Some(123430)), |
There was a problem hiding this comment.
| /// Allows deriving traits as per `CoercePointee` specification | |
| (unstable, derive_coerce_pointee, "1.79.0", Some(123430)), |
per @compiler-errors's comment
|
@bors r+ |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (81d6652): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (secondary -3.2%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (secondary 9.3%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 783.479s -> 782.673s (-0.10%) |
|
The issue description (first comment) does not match the implementation. Can we update it? |
|
Thank you for pointing it out! I have updated the description. There had been flips and flops on terminology back then. This will finally set the record straight. |
As per resolution #129104 we will rename the macro to better reflect the technical specification of the feature and clarify the communication.
SmartPointeris renamed toCoercePointee#![feature(derive_smart_pointer)]gate is renamed to#![feature(derive_coerce_pointee)].SmartPointerin the file names are renamed accordingly.r? @compiler-errors
cc @nikomatsakis @Darksonn