Tracking issue for RFC 3621: `derive(CoercePointee)`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is a tracking issue for #[derive(CoercePointee)].
The feature gate for the issue is #![feature(derive_coerce_pointee)].
It was formerly known as:
#[derive(UnsizeInner)]#[derive(SmartPtr)]#[feature(derive_smart_pointer)]
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
- Implement the language experiment.
- Accept an RFC.
- Decide on a final name.
- Adjust documentation (see instructions on rustc-dev-guide).
- Stabilization PR.
Unresolved Questions
- is the derive name good? Should it be more general than "smart pointer"? (Do not discuss on this issue, open a zulip thread or separate GitHub issue)
Related
- https://github.com/rust-lang/rfcs/pull/3621
- https://github.com/rust-lang/rust/pull/125575
- https://github.com/rust-lang/rust/pull/125048
- https://github.com/rust-lang/rust/pull/123472
- https://github.com/rust-lang/rust/pull/127283
- https://github.com/rust-lang/rust/issues/136702
- https://github.com/rust-lang/rust/pull/147068
- https://github.com/rust-lang/rust/issues/127323
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start with RFC 3621 and the linked implementation and stabilization PRs, then review the rustc-dev-guide documentation and stabilization checklists; done means completing the documentation work and the remaining stabilization requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100