Join GitHub today
[Stabilization] Stablize using some arbitrary self types defined in std #55786
This is a proposal to stabilize a subset of the
Stabilized feature or APIs
Today, only the following types are allowed as self types unless the user uses
We've long desired to extend this set to all pointer types defined in std, and
The new self types that will be enabled by this stabilization are:
Additionally, all of these receiver types except for
Object safety of raw pointer types
By making pointers object-safe, we have introduced an additional requirement on
As an alternative, we could possibly restrict this to only allowing raw
Team member @withoutboats has proposed to merge this. The next step is review by the rest of the tagged teams:
Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!
See this document for info about what commands tagged team members can give me.
@rfcbot concern raw-pointers-metadata
I don't have a position, but the lang team should decide: shall we require that raw wide pointers (like
Do we need this exception given unsized rvalues (#48055)?
The raw pointers don't implement
I agree with @joshtriplett here re. raw pointers; I don't think sufficient justification is given for either approach mentioned so it is hard to determine what the right course of action is.
Tho I wonder a bit about process here... we haven't accepted any RFC to stabilize the rest either yet... is that OK?