Tracking Issue for unsized const parameter types: `feature(unsized_const_params)`
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 supporting unsized types in const generics.
The feature gate for the issue is #![feature(unsized_const_params)].
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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
Steps
Most of the work here will be coordinated in the #project-const-generics stream on zulip.
- Experiment with supporting
{ *"hi" }as a const argument toconst N: str - Resolve #120961 somehow (e.g. by forbidding references if the previous step works out)
- Author an RFC for the feature
- Adjust documentation (see instructions on rustc-dev-guide)
- Stabilization PR (see instructions on rustc-dev-guide) merges the
ConstParamTyandUnsizedConstParamTytraits
Unresolved Questions
- Can we forbid references and support
!Sizedtypes some other way
Implementation history
- Feature was split out of
adt_const_paramsin #127722
cc @rust-lang/project-const-generics
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
Start with the checklist in issue #128028 and the unresolved question about references and !Sized types. Coordinate in the #project-const-generics Zulip stream, then review the linked rustc-dev-guide instructions for RFC, documentation, and stabilization work. Done means the relevant design and implementation milestones are completed and the stabilization PR merges the two traits.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100