Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Highlights from the 2026 goals

There are a total of 50 planned for this year. That’s a lot! You can see the complete list, but to help you get a handle on it, we’ve selected a few to highlight. These are goals that will be stabilizing this year or which we think people will be particularly excited to learn about.

Important: You have to understand the nature of a Rust goal. Rust is an open-source project, which means that progress only happens when contributors come and make it happen. When the Rust project declares a goal, that means that (a) contributors, who we call the task owners, have said they want to do the work and (b) members of the Rust team members have promised to support them. Sometimes those task owners are volunteers, sometimes they are paid by a company, and sometimes they supported by grants. But no matter which category they are, if they ultimately are not able to do the work (say, because something else comes up that is higher priority for them in their lives), then the goal won’t happen. That’s ok, there’s always next year!

Cargo improvements

Stabilize cargo-script

Ed Page (point of contact)

Stabilize support for “cargo script”, the ability to have a single file that contains both Rust code and a Cargo.toml.

Stabilize public/private dependencies Help wanted

Implement and stabilize the MVP of public dependencies described in RFC #3516. Public dependencies allow crates to declare dependencies whose types are meant to be exposed in the public API.

Language changes

Const Generics

Boxy (point of contact), Niko Matsakis (lang champion)

Extend const generics in two independent directions, both aiming for stabilization:

  • adt_const_params: Allow structs and enums as const generic arguments, not just integers.
  • min_generic_const_args: Allow associated constants as const generic arguments (e.g., Foo<T::ASSOC_CONST>).

We will also model const generics in a-mir-formality and experiment with upstreaming those changes into the Rust specification. This work also serves as a forcing function for advancing a-mir-formality and its integration into the Rust specification.

Stabilize the next-generation trait solver

lcnr (point of contact), Niko Matsakis (lang champion), lcnr (types champion)

Stabilize -Znext-solver=globally, replacing the existing trait solver implementation entirely.

Sized Hierarchy and Scalable Vectors

David Wood (point of contact), David Wood (compiler champion), Niko Matsakis (lang champion), Amanieu d’Antras (libs-api champion), lcnr (types champion)

Over the next year, we will build on the foundational work from 2025 to stabilize the Sized trait hierarchy and continue nightly support for scalable vectors:

  • Stabilize the refined Sized trait hierarchy (without constness), unblocking extern types
  • Propose and implement const Sized to support scalable vectors
  • Achieve RFC acceptance for [rfcs#3838] (Scalable Vectors)
  • Land SVE types and intrinsics in stdarch for nightly experimentation
  • Continue addressing stabilization blockers for SVE itself
  • Begin design work for supporting the Scalable Matrix Extension (SME)

The const Sized work (Part II of [rfcs#3729]) is deferred to a future goal, allowing us to deliver value sooner through the trait hierarchy stabilization. This future work interacts with ongoing const generics efforts, as const Sized depends on progress in const traits.

Other

Stabilize MemorySanitizer and ThreadSanitizer Support

Jakob Koschel (point of contact)

Stabilize the MemorySanitizer and ThreadSanitizer support. This includes fixing open bugs for the sanitizers to open a path for stabilization and the necessary infrastructure changes to provide precompiled and instrumented standard libraries for the sanitizers.

Stabilize Cargo SBOM precursor Help wanted

Progress towards an MVP version of Cargo SBOM support by resolving known issues in Cargo’s SBOM precursor feature and finalizing the RFC.

Wasm Components

Yoshua Wuyts (point of contact)

In 2026 we want to improve the state of Wasm Component support in Rust. This means adding and stabilizing three new compiler targets, as well as begin experimentation with Wasm-specific language features.