rust-lang/rust 1.100.0
Comments on “rust-lang/rust 1.100.0”
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.0 stabilizes the never type (!), after ten years and five failed attempts according to the Rust blog, along with custom allocators for Box, Vec and related types. Cargo adds its own lint system, including an unused-dependency check, and minimum publish age settings that let the resolver skip recently published crate versions. Check builds for breakage: Cargo's intermediate build directory layout changed, never type fallback is now ! on all editions, closures capture more precisely in if let, and some ARM target-feature settings are now hard errors.
Why it ranked
No. 6 of 137 with a score of 0.71. The panel rated it highest on new information (0.93) and practical relevance (0.80), lowest on technical depth (0.63). Placed No. 6, No. 8 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Major Rust stable release notes with stabilized allocator APIs, never type and Cargo changes. Broadly relevant to builders, but it is a changelog list with little depth on each item.
- AI judgeJudge 3gpt-5.6-luna
- A major Rust compiler, standard-library, Cargo, and platform release with actionable compatibility notes and allocator/dependency-management changes. It is highly relevant to Rust developers, though less consequential outside that ecosystem.
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.3
- Significance0.67
- Reader interest0.73
- Audience breadth0.71
- Practical relevance0.80
- Substantiated0.74
- Technical depth0.63
- New information0.93
- Counts against: Promotional0.05
- Counts against: Overclaim0.09
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.72 | 0.60 | 0.68 | 0.67 | 0.13 | +0.24 | +0.160 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.56 | 0.80 | 0.82 | 0.73 | 0.26 | +0.26 | +0.189 |
| Audience breadthHow many people who build technology does it concern? | 0.67 | 0.80 | 0.67 | 0.71 | 0.13 | +0.13 | +0.093 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.82 | 0.80 | 0.78 | 0.80 | 0.04 | +0.22 | +0.176 |
| 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.69 | 0.70 | 0.82 | 0.74 | 0.13 | +0.05 | +0.037 |
| Technical depthHow technically substantive is it? | 0.62 | 0.60 | 0.68 | 0.63 | 0.08 | +0.05 | +0.032 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.90 | 1.00 | 0.93 | 0.12 | +0.05 | +0.046 |
| 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.05 | 0.05 | 0.04 | 0.05 | 0.01 | −0.19 | −0.009 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.13 | 0.10 | 0.03 | 0.09 | 0.10 | −0.11 | −0.010 |
| Sum of contributions | +0.714 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.714 | ||||||
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.
<a href="https://rubric.hrih.si/editions/2026-11-13/6/"><img src="https://rubric.hrih.si/badge/2026-11-13/6.svg" alt="Ranked #6 on Rubric, 13 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 3 matches source · 5 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceVersion
Rust 1.100.0 stabilizes the never type.
The cited source says the same thing.
The article says “Stabilize never type”
The source says “stabilizes the [never type](https://doc.rust-lang.org/stable/std/primitive.never.html) (aka”
Source cited by the article: github.com/rust-lang/rust/pull/155499
Couldn’t checkVersion
Rust 1.100.0 stabilizes custom allocators.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Stabilize custom allocators”
The source says No passage could be compared.
Source cited by the article: github.com/rust-lang/rust/pull/156882
Couldn’t checkVersion
Rust 1.100.0 promotes wasm32-wasip3 to Tier 2 platform support.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Promote wasm32-wasip3 to Tier 2”
The source says No passage could be compared.
Source cited by the article: github.com/rust-lang/rust/pull/161940
Couldn’t checkVersion
Rust 1.100.0 adds a new Tier 3 target, powerpc64-sony-ps3.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Add new Tier 3 target powerpc64-sony-ps3”
The source says No passage could be compared.
Source cited by the article: github.com/rust-lang/rust/pull/162072
Matches sourceVersion
Cargo introduced its own linting system, with some warnings now emitted as lints controllable in the [lints.cargo] table, including a new cargo::unused_dependencies lint.
The cited source says the same thing.
The article says “Introduced Cargo's own linting system: some Cargo warnings are now emitted as lints that users can control in the [lints.cargo] table”
The source says “We are adding a linting system to workspaces and packages controlled by `[lints.cargo”
Source cited by the article: github.com/rust-lang/cargo/pull/17298
Matches sourceVersion
Cargo introduced minimum publish age configurations (dependency cooldowns), where the resolver ignores versions published more recently than the configured age unless already in Cargo.lock.
The cited source says the same thing.
The article says “the resolver ignores versions published more recently than that, unless they are already in Cargo.lock”
The source says “To ensure dependencies have had a chance to be scanned, a user can set”
Source cited by the article: github.com/rust-lang/cargo/pull/17335
Couldn’t checkDate
From Rust 1.94 up to 1.100, a number of ARMv7-A hardfloat targets required the VFPv3-D32 FPU as a minimum because they erroneously had the d32 feature in their baseline feature list.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “From version 1.94 up to 1.100 a number of ARMv7-A hardfloat targets required the VFPv3-D32 FPU as a minimum”
The source says No passage could be compared.
Source cited by the article: github.com/rust-lang/rust/pull/160911
Couldn’t checkVersion
The Rust standard library now uses Unicode version 18.0.0.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The standard library now uses Unicode version 18.0.0”
The source says No passage could be compared.
Source cited by the article: doc.rust-lang.org/stable/std/primitive.char.html
Also covered by
Elsewhere
Elsewhere: HN 314 pts, front page
Recorded for context only, checked 15 Nov 2026, 20:42 UTC. It played no part in the ranking.