Will Rust support specialization on stable by end of 2026?

Ṁ110Ṁ388

2027

chance

ALL

RFC: https://rust-lang.github.io/rfcs/1210-impl-specialization.html

GitHub issue: https://github.com/rust-lang/rust/issues/31844

Update 2026-02-13 (PST) (AI summary of creator comment): The implementation does not have to match the RFC exactly, but negative trait impls alone would not count.

The core requirement is: multiple impls must be allowed as long as they each apply to progressively narrower sets of types.

As a concrete test case: the first AddAssign example in the RFC must be supported by whatever mechanism Rust implements.

Market context

Programming

Rust

Get

1,000

to start trading!

People are also trading

Will Unreal Engine officially support development in Rust before 2030?

73% chance

Will this issue with Rust's type safety be fixed before the release of edition 2027?

65% chance

Will Rust be ranked in the top 10 programming languages by the year 2030? 🦀🚀

86% chance

Will Rust become the main programming language for LLMs?

22% chance

Which of these features/concepts will be added to the official Rust game by Facepunch before EOY 2027?

Will Microsoft replace all C/C++ code with rust by 2030?

6% chance

Will more professional devs use Rust than C++ in the 2030 StackOverflow developer survey?

56% chance

Will Stability AI fold by 2028?

Sort by:

What counts as "supporting specialization"? Does Rust have to implement precisely that RFC? Or would it suffice to have a mechanism that allows "if the type supports this trait do X, if the type doesn't support this trait do Y"?

@josh It doesn't have to be exactly this RFC but I think negative trait impls by itself would not count. The core spirit of specialization is being able to have multiple impls as long as they each apply to a narrower and narrower set of types. As a concrete criteria the first AddAssign example in the RFC should be handled which I don't believe can be done with just your mechanism.