Description
This is a tracking issue for work on pin ergonomics.
The feature gate for the issue is #![feature(pin_ergonomics)]
.
Design sketch
The basic pin projection rules that we're working toward are:
- The type
&pin mut T
coerces to&mut T
ifT: Unpin
. - The type
&mut T
coerces to&pin mut T
ifT: Unpin
. - If
T: Drop
, thenimpl !Unpin for T
is only allowed ifDrop
is implemented withfn drop(&pin mut self)
. - Projection of
&pin mut T
to&pin mut T.U
is allowed ifT: !Unpin
. - Projection of
&pin mut T
to&mut T.U
is allowed ifU: Unpin
.
These rules are factored differently (using coercions and the fact that we haven't stabilized negative impls yet), but have the same effect as the rules in Niko's MinPin proposal.
Beyond pin projection, the basic overall idea of pin ergonomics is that &pin mut T
(and &pin const T
) should be integrated in the same sense as &mut T
, in that reborrowing works, and that the borrow checker will track and ensure that once a &pin mut T
is taken (even if no longer live) that we can't later get a &mut T
or move T
.
About tracking issues
Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
- Approve as lang experiment.
- We accepted this experiment in the 2024-09-18 lang triage meeting.
- Accept an RFC.
- Implement pin reborrowing in nightly.
- Implement pin autoref in nightly.
- Implement
&pin const
/&pin mut
constructor syntax in nightly. - Implement
&pin const
/&pin mut
type syntax in nightly. - Implement
&pin const self
/&pin mut self
argument syntax in nightly. - Implement
drop
changes in nightly. - Investigate affordances for unsafe parts of the
Pin
API. - Add documentation to the dev guide.
- See the instructions.
- Add documentation to the reference.
- See the instructions.
- Add formatting for new syntax to the style guide.
- See the nightly style procedure.
- Stabilize.
- See the instructions.
Unresolved Questions
TODO.
Related
TODO.
cc @eholk @rust-lang/lang
Sub-issues
Metadata
Metadata
Assignees
Labels
Type
Projects
Status