Rust 1.100.0 ships with stabilized custom allocators and never type
connpass.com

Rust 1.100.0 ships with stabilized custom allocators and never type

Archived — this story has rotated out of today’s deck. It is kept here in full.

The gist

The Rust project released version 1.100.0 on November 12, with 5325 commits since the last release.
The update stabilizes custom allocators, an API tied to Microsoft-reported soundness bugs.

Background

Rust is a programming language whose release notes for 1.100.0 list language changes including stabilizing the never type and extern "custom", compiler changes such as -Cprofile-sample-use, and stabilized APIs including custom allocators. The release follows Microsoft FORGE Lab, a Microsoft research lab, reporting memory-safety issues in Rust's standard libraries, including cases where code written entirely in safe Rust can trigger undefined behavior. One of those findings, a BTreeMap::insert case that was unsound when a custom allocator unwinds, shaped the rule that allocator implementors must never unwind from the trait's methods or from drop.

How it unfolded

  1. Sep 25, 2026Rust 1.100.0 was branched from master.
  2. Nov 9, 2026Microsoft FORGE's findings on Rust standard library soundness bugs were reported, ahead of the scheduled November 12 release that stabilizes the Allocator API involved in one finding.
  3. Nov 10, 2026Release notes for Rust 1.100.0, dated 2026-11-12, were shared on X.
  4. Nov 12, 2026Rust 1.100.0 was released by rustbot, with 5325 commits to main since the previous release.
  5. Nov 16, 2026An unofficial online release party hosted by estie is scheduled for 18:30, with 10 of 80 participant slots filled.

Key terms

custom allocators
A C standard library function that allocates a block of dynamic memory.
never type
A type that is a subtype of every other type, having no values.
soundness
A property of a logical system meaning everything it proves is true.

Source: Wikipedia

Who’s saying what

Analysts
Microsoft FORGE Lab reported that code written entirely in safe Rust can trigger undefined behavior in the standard libraries, and said its Hyenas AI tooling helped find candidates while humans investigated, reproduced and assessed the bugs and worked with Rust maintainers on fixes.
Community
A forum poster asked whether enabling the next solver by default in orphanck means the next-generation trait solver arrives with 1.100; a reply said orphanck is part of trait impl coherence checking and full stabilization is expected to reach stable in 1.102.

Still unverified

As of November 9, the 1.100.0 release and its inclusion of custom allocator stabilization were still scheduled and not yet shipped; a forum discussion states the next-generation trait solver stabilization "might land in 1.102".

Sources

See today’s stories in the app Gistline — free on the App Store