initial draft for 2026 project goals#3935
Open
nikomatsakis wants to merge 8 commits intorust-lang:masterfrom
Open
initial draft for 2026 project goals#3935nikomatsakis wants to merge 8 commits intorust-lang:masterfrom
nikomatsakis wants to merge 8 commits intorust-lang:masterfrom
Conversation
Contributor
Author
FCP ProcessPer our usual process, to be accepted, we require checkboxes from the leads of every team with a "team ask". Checkboxes from other members are encouraged but not required. book
bootstrap
cargo
clippy
compiler
crate-maintainers
crates-io
edition
fls
infra
lang
lang-docs
leadership-council
libs
libs-api
opsem
project-exploit-mitigations
rustdoc
rustfmt
rustup
spec
style
testing-devex
types
wg-mir-opt
wg-parallel-rustc
|
lqd
reviewed
Mar 25, 2026
RalfJung
reviewed
Mar 26, 2026
| | | | [lang][] | [Tyler Mandry][] | | ||
| | | | [compiler][] | *n/a* | | ||
| | | | [libs][] | *n/a* | | ||
| | | | [opsem][] | *n/a* | |
Member
There was a problem hiding this comment.
It's still unclear to us what the opsem ask even is here. This doesn't sound like a goal that has opsem aspects.
| | [Continue resolving `cargo-semver-checks` blockers for merging into cargo](https://rust-lang.github.io/rust-project-goals/2026/cargo-semver-checks.html) | [Predrag Gruevski][] | [cargo][] | *n/a* | | ||
| | | | [rustdoc][] | *n/a* | | ||
| | [Improving Unsafe Code Documentation in the Rust Standard Library](https://rust-lang.github.io/rust-project-goals/2026/improve-std-unsafe.html) | @hxuhack | [libs][] | *n/a* | | ||
| | | | [opsem][] | *n/a* | |
Member
There was a problem hiding this comment.
The opsem ask was unclear to us here, this seems to be mostly about library documentation. Without a libs champion, is this goal even happening?
There was a problem hiding this comment.
The asks are all Small, so the goal doesn't need champions
| | [C++/Rust Interop Problem Space Mapping](https://rust-lang.github.io/rust-project-goals/2026/interop-problem-map.html) | [teor][] | [compiler][] | *n/a* | | ||
| | | | [lang][] | *n/a* | | ||
| | | | [libs-api][] | *n/a* | | ||
| | | | [opsem][] | *n/a* | |
Member
There was a problem hiding this comment.
We haven't found someone who's able to dedicate substantial amounts of time for this. The usual kind of opsem questions/feedback we handle on Zulip are fine of course.
There was a problem hiding this comment.
That's alright because the ask is Small.
lcnr
approved these changes
Apr 3, 2026
tmandry
reviewed
Apr 6, 2026
|
|
||
| Finally, the [Sized trait hierarchy](https://rust-lang.github.io/rust-project-goals/2026/scalable-vectors.html) work will stabilize a richer set of sizing traits, which unblocks [extern types](https://github.com/rust-lang/rfcs/pull/1861) — another long-requested feature. Today, `?Sized` conflates "unsized but has metadata" with "truly sizeless." The new hierarchy distinguishes these cases. This same work is also laying the foundation for scalable vector support (Arm SVE), where vector sizes depend on the CPU rather than being fixed at compile time. | ||
|
|
||
| ## Going "beyond the `&`" with better integration for custom pointer types |
Member
There was a problem hiding this comment.
This is missing several of the goals listed under the roadmap: https://rust-lang.github.io/rust-project-goals/2026/roadmap-beyond-the-ampersand.html#how-we-get-there
- Reborrow traits
- In-place init
- Supertrait auto impl
Of the above I'd say the Reborrow traits are 100% this, while the other two are more tangentially related.
Co-authored-by: lcnr <rust@lcnr.de>
Co-authored-by: Tyler Mandry <tmandry@gmail.com>
nxsaken
reviewed
Apr 7, 2026
Co-authored-by: Nurzhan Saken <nurzhan.sakenov@gmail.com>
nxsaken
reviewed
Apr 8, 2026
Co-authored-by: Nurzhan Saken <nurzhan.sakenov@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
View all comments
Establish the initial round of Rust Project Goals for 2026 along with a set of current roadmaps, which describe multi-year development arcs.
New Rust Project Goals may be added over the course of the year but only if all required resources (champions, funding, etc) are already known.
Important
When responding to RFCs, try to use inline review comments (it is possible to leave an inline review comment for the entire file at the top) instead of direct comments for normal comments and keep normal comments for procedural matters like starting FCPs.
This keeps the discussion more organized.
Rendered
Note
Concerns (0 active)
specialization-goalresolved in this commentManaged by
@rustbot—see help for details.