$ the-wire · showcase
Rust removes `type const`, crates.io registry ticks over
By RepoJournal · Filed · About Rust · Composed from the cited sources · methodology
The compiler merged a change that removes `type const` from the language, while crates.io and libc kept to routine dependency and platform work.
Rust's auto-merge picked up the removal of `type const`, the headline change of the day for the language itself [1]. The same merge implements `#[rustc_always_gca]` as part of the broader const-generics design work, so anyone tracking generic const arguments should read the tracking issue before building against nightly [1]. The PR description frames it as two changes: "yeet `type const`" plus the new attribute.
The crates.io index absorbed a batch of crate updates through bors, covering `hk`, `vize_fresco`, `vize_musea`, `vize_atelier_sfc`, and `vize_atelier_ssr` [2][3][4][5][6]. These are registry entries, not crate releases with their own changelogs, so the signal is that the registry is moving normally.
On the crates.io application side, Renovate filed the usual dependency bumps: `@types/node` to 24.13.4 [7], the unocss monorepo to 66.10.1 [8], `chromatic` to 18.7.4 [9], and `valibot` to 1.5.0 [10]. Separately, a test fix for the Svelte `Tooltip` delay switched to fake timers: the test now advances them to verify the tooltip stays hidden at 199 ms and appears at 200 ms, replacing a timing-sensitive assertion [11].
In `libc`, the Linux bindings gained `FUTEX_ROBUST_UNLOCK` and `FUTEX_ROBUST_LIST32`, constants added in Linux 7.2 [12][13]. The CI story is quieter: `i686-pc-windows-msvc` is now tested without host tools, per RFC 3999 [14][15]. None of these are urgent; they are the ordinary shape of a working day across the Rust org.
Action items
- → Track the const-generics tracking issue before relying on `type const` on nightly rust-lang/rust [plan]
- → No action needed on the crates.io dependency bumps; they are routine Renovate updates rust-lang/crates.io [monitor]
- → Update libc consumers that need `FUTEX_ROBUST_UNLOCK` or `FUTEX_ROBUST_LIST32` once the release lands rust-lang/libc [plan]
References
- [1] Auto merge of #162517 - khyperia:yeet-type-const, r=BoxyUwU ↗ rust-lang/rust
- [2] Update crate `hk` ↗ rust-lang/crates.io-index
- [3] Update crate `vize_fresco` ↗ rust-lang/crates.io-index
- [4] Update crate `vize_musea` ↗ rust-lang/crates.io-index
- [5] Update crate `vize_atelier_sfc` ↗ rust-lang/crates.io-index
- [6] Update crate `vize_atelier_ssr` ↗ rust-lang/crates.io-index
- [7] Update dependency @types/node to v24.13.4 ↗ rust-lang/crates.io
- [8] Update unocss monorepo to v66.10.1 ↗ rust-lang/crates.io
- [9] Update dependency chromatic to v18.7.4 ↗ rust-lang/crates.io
- [10] Update dependency valibot to v1.5.0 ↗ rust-lang/crates.io
- [11] svelte: Use fake timers in `Tooltip` delay test ↗ rust-lang/crates.io
- [12] linux: Add FUTEX_ROBUST_UNLOCK and FUTEX_ROBUST_LIST32 ↗ rust-lang/libc
- [13] linux: Add FUTEX_ROBUST_UNLOCK and FUTEX_ROBUST_LIST32 ↗ rust-lang/libc
- [14] ci: Test `i686-pc-windows-msvc` as without host tools ↗ rust-lang/libc
- [15] ci: Test `i686-pc-windows-msvc` as without host tools ↗ rust-lang/libc