Looking for funding
The goals below are looking for funding. If you might be interested in helping to fund a goal, please join the rust-lang Zulip and post a message in the #project-goals/2026-workshop channel or write to the goals team at goals-team@rust-lang.org.
| Goal | Cost | Status | What and why |
|---|---|---|---|
| Constify all the things | TBD | ||
| Architectural groundwork for expansion-time evaluation | TBD | 🔍 Looking | Lay the architectural groundwork for functions that can be evaluated during macro expansion. |
| Fast Builds | $75,000 | ||
Improve rustc_codegen_cranelift performance | $75,000 | ✅ Finalized | This goal aims to improve the rust development experience through faster incremental code generation with rustc_codegen_cranelift. |
| Just add async | TBD | ||
| Box notation for dyn async trait | TBD | 🔍 Looking | Enable dyn dispatch for async traits via .box notation |
| Other goals | $50,000 | ||
| Async statemachine optimisation | TBD | 💬 Under discussion | Add optimisations to the coroutine MIR transform to elide or simplify the generated statemachines. |
| Control over Drop semantics | TBD | 💬 Under discussion | Allow users to easily control the drop semantics of struct fields, letting them change drop order, and disable recursive destructors to make working with cross-language bindings easier. |
| Stabilize concrete type specialization | TBD | 💬 Under discussion | 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. |
| Stabilize the Try trait | TBD | 💬 Under discussion | Stabilize the Try trait, which customizes the behavior of the ? operator. |
Stabilizing f16 | $25,000 | ✅ Finalized | In recent years we’ve seen increasing hardware support for the f16 and f128 float types. |
Explicit tail calls & loop_match | $25,000 | ✅ Finalized | It is important that rust generates efficient code. |
| Total | $125,000 |