-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
Open
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCF-ergonomic_clones`#![feature(ergonomic_clones)]``#![feature(ergonomic_clones)]`T-langRelevant to the language teamRelevant to the language teamT-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.
Description
This is a tracking issue for ergonomic reference counting, including:
- Simplify lightweight clones, including into closures and async blocks rfcs#3680
- Ergonomic ref-counting: RFC decision and preview rust-project-goals#107
...and other work.
The feature gate for this issue is #![feature(ergonomic_clones)].
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.
- Modify the MIR building to create a customer terminator for "use" that selects between copy/clone/move post-monorphization
- Add tests and support for const use closures
- Resolve Test interaction between RFC 2229 migration and
useclosures #138101 - Accept an RFC.
- Implement in nightly.
- Finalize opsem (What is the operational spec for
useexpressions? unsafe-code-guidelines#564) - 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
- Name of
UseClonedtrait which signalsx.usetoclone - Precise set of
UseClonedimpls -- in particular any blanket impls we ought to be concerned about? - should
x.usework on!Clonetypes? Currently the impl just generates a move
Related
cc @spastorino @jkelleyrtp @rust-lang/lang
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCF-ergonomic_clones`#![feature(ergonomic_clones)]``#![feature(ergonomic_clones)]`T-langRelevant to the language teamRelevant to the language teamT-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.