Specialization: minimal implementation
Open
@jackh726 is already working on this.
Since Jun 29, 2026.
C-tracking-issue
T-lang
T-libs
T-opsem
T-types
- Dominant language
- Rust
- Stars
- 173
- Forks
- 119
- Avg merge
- 6h 31m
- Merged PRs (30d)
- 20
Description
| Metadata | |
|---|---|
| Point of contact | @jackh726 |
| Team(s) | lang, libs, opsem, types |
| Goal document | 2026/specialization |
Summary
Work over this year will be done to identify key use cases of specialization and possible designs that could address them, and to implement a minimal, sound design for future stabilization.
Tasks and status
Note: we have updated the body to match the 2026 goal. Your original text is preserved below.
| Metadata | |
|---|---|
| Point of contact | @jackh726 |
| Team(s) | lang, libs, opsem, types |
| Goal document | 2026/specialization |
Summary
Follow stabilization of the new trait solver this year by stabilizing a subset of specializing impls: Impls that follow the [always applicable][always applicable] rule. This roughly corresponds to specializing trait impls on concrete types.
Tasks and status
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.