Edition of Tuesday 17 November 2026

Rust 1.100 stabilizes Never Type after 10 years; Cargo holds new releases

Comments on “Rust 1.100 stabilizes Never Type after 10 years; Cargo holds new releases”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Rust 1.100 stabilizes the Never Type ! and core parts of the Allocator API, so per-collection allocators for Vec and Box no longer need Nightly. Cargo gains a configurable minimum publish age, which skips freshly released crate versions not already in Cargo.lock, and it only works where the registry records publish times. In editions before 2024 the never-type fallback changes from () to !, which can break code that ignores a generic result. Heise advises checking CI logs for the related lints before upgrading.

Read the original at heise.de. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 6 of 122 with a score of 0.71. The panel rated it highest on technical depth (0.84) and practical relevance (0.83), lowest on new information (0.58). The judges disagreed most on new information (spread 0.78), so the story is marked contested. Placed No. 6, No. 10 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Official Rust 1.100 release notes covering stabilized Never Type, Allocator API, and Cargo supply-chain features; highly practical for builders, well substantiated with examples and links, not promotional.
AI judgeJudge 3gpt-5.6-luna
A technically detailed Rust release overview with actionable migration guidance, allocator changes, Cargo supply-chain defenses, and compatibility risks. It is highly relevant to Rust developers, though the release itself already appears in the recent-coverage list.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.71total under rubric v2.3Contestedjudges differ by 0.78 on new information

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.66
  • Reader interest0.77
  • Audience breadth0.62
  • Practical relevance0.83
  • Substantiated0.77
  • Technical depth0.84
  • New information0.58
  • Counts against: Promotional0.04
  • Counts against: Overclaim0.15

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.690.600.680.660.09+0.24+0.158
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.690.800.820.770.13+0.26+0.200
Audience breadthHow many people who build technology does it concern?0.590.700.580.620.12+0.13+0.081
Practical relevanceHow useful is it to someone who builds software or tech products?0.870.850.780.830.09+0.22+0.183
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.650.800.860.770.21+0.05+0.039
Technical depthHow technically substantive is it?0.900.850.780.840.12+0.05+0.042
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.730.900.120.580.78 , above the contested threshold+0.05+0.029
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.050.050.030.040.02−0.19−0.008
OverclaimDo the headline or conclusions claim more than the body supports?0.260.100.080.150.18−0.11−0.016
Sum of contributions+0.708
Claim-check penalty0.000
Total, as published0.708

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #6 on Rubric, 17 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-17/6/"><img src="https://rubric.hrih.si/badge/2026-11-17/6.svg" alt="Ranked #6 on Rubric, 17 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: 4 matches source · 1 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Matches sourceVersion

    Rust 1.100.0 stabilizes the Never Type ! and key parts of the Allocator API, which previously required the Nightly toolchain.

    The cited source says the same thing.

    The article says

    “The biggest change is the Never Type !, which, along with key parts of the Allocator API, is now available in stable”

    The source says

    “After 10 years and 5 failed stabilization attempts, the never type is finally stable”

    Source cited by the article: blog.rust-lang.org/2026/11/12/Rust-1.100.0

  2. Matches sourceVersion

    Cargo in Rust 1.100 can hold back new package versions for a configurable period and warns about unused dependencies.

    The cited source says the same thing.

    The article says

    “Cargo package manager, which can now hold back new package versions for a configurable period to catch compromised releases”

    The source says

    “Rust 1.100 stabilizes Cargo's min-publish-age aware dependency resolution, which lets you wait for that window before it picks up newly published versions”

    Source cited by the article: blog.rust-lang.org/2026/11/12/Rust-1.100.0

  3. No source givenDate

    std::convert::Infallible was introduced in Rust 1.34 in 2019 as a substitute for the Never Type.

    The article gives no link or citation for it.

    The article says

    “The standard library therefore introduced a substitute in 2019, with Rust 1.34: std::convert::Infallible, an enum with no variants”

    The source says

    No source to compare with.

  4. Couldn’t checkVersion

    In Rust 1.100, Infallible becomes just another name for !, and existing APIs continue to work unchanged.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “In Rust 1.100, Infallible is now just another name for !, and existing APIs continue to work unchanged”

    The source says

    No passage could be compared.

    Source cited by the article: blog.rust-lang.org/2026/11/12/Rust-1.100.0

  5. Matches sourceCausal conclusion

    In editions before 2024, Rust 1.100 changes the Never Type fallback from () to !, which can cause compiler errors in rare cases.

    The cited source says the same thing.

    The article says

    “In editions before 2024, Rust 1.100 changes this fallback from () to”

    The source says

    “Never type (!) to any type (“never-to-any”) coercions now fall back to never type (!) rather than to unit type (()) on all editions”

    Source cited by the article: doc.rust-lang.org/edition-guide/rust-2024/never-type-fallback.html

  6. Couldn’t checkDate

    Since 2024 the compiler has warned when code uses the fallback in a way that would break with the change.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Since 2024, the compiler has warned when code uses the fallback in a way that would break with the change”

    The source says

    No passage could be compared.

    Source cited by the article: lwn.net/Articles/1091015

  7. Couldn’t checkCausal conclusion

    RFC 3923 cites recent attacks on the npm ecosystem as the impetus for Cargo's publish-age waiting period.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “The underlying RFC 3923 cites the latest attacks on the npm ecosystem as the impetus”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/rust-lang/rfcs/pull/3923

  8. Matches sourceVersion

    The 32-bit Windows targets i686-pc-windows-msvc and i686-pc-windows-gnu lose their host tools, so a Rust toolchain can no longer be installed on 32-bit Windows.

    The cited source says the same thing.

    The article says

    “The 32-bit Windows targets i686-pc-windows-msvc and i686-pc-windows-gnu are losing their host tools, so a Rust toolchain can no longer be installed on”

    The source says

    “After Rust 1.100, it will no longer be possible to install toolchains on 32-bit Windows hosts”

    Source cited by the article: blog.rust-lang.org/2026/10/02/demoting-i686-windows-targets-to-std-only

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN —

Recorded for context only, checked 17 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Rust 1.100 stabilizes Never Type after 10 years; Cargo holds new releases”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.