Every so often I am told about some maths fact that I can only assume someone went to prison for discovering
we need a new in-joke after a certain type is not named anymore after the date of it's stabilization 😆
Every so often I am told about some maths fact that I can only assume someone went to prison for discovering
okay sure, igaf whether this compiles
— lcnr, at #t-types/call-for-participation > higher-ranked trait object failure to prove auto-trait @ ![]()
The noise canceling phone subsidy propagandist was me.
@llogiq on the RustConf Discord
Now you don't have to self-nominate ![]()
operational pedantics
turns out o-ped is canon now, TWIR has decreed
it's an old one from "let's get rusty" but I only just heard it: Rust Ruined My Career (I Can't Go Back) (very tongue-in-cheek!)
The community is obnoxiously helpful. I asked a simple question on the Rust community Discord server. What is the best way to read a file in Rust? I expected a straightforward response. Instead, I got back a 2,000-word essay on the inner workings of IO, buffering, error handling, and ownership, plus links to four different blog posts and three different approaches depending on file size, and a working code example.
...
The Rust community has weaponized education against me. I'm now a better engineer than I was yesterday against my will.
cursed knowledge helps with breaking things
There's another good qoute a few lines down:
opsem is the crusher of dreams
the language has big plans
or at least, big requests to plan
— Clar Fon, on the many many topics that needs discussion in the language team. #t-lang/meetings > Triage meeting 2026-09-30 @ ![]()
And from Clar Fon again... This time in yesterday's design meeting:
in stdlib we can make up our own compiler features if we need to, but in user-land that's not possible
(is there a "most nominations in one week" prize?)
Responding to my comment that "rust-lang/rust#159295 implements rust-lang/rfcs#3753 by lowering SomeType { .. } to PatKind::Wild in THIR", @RalfJung replied:
I see. That's... a kind of wild lowering.
(compilers are already expected to take 100% CPU anyway, so just let them mine some bitcoin)
I was joking about this being QOTW, but ok ![]()
There ain't no rules here in Quote of the Week - it's survival of the wittest
You knew this was going to get proposed:
Most of the time I don't mean it, but I kinda suspected this time ![]()
we need a new in-joke after a certain type is not named anymore after the date of it's stabilization
we need a new in-joke after a certain type is not named anymore after the date of it's stabilization 😆
I think the links got munged there...