<Quxxy2> But in general, invisible dependencies make your code more brittle and harder to understand
<Quxxy2> It's like the One Ring: being invisible is handy, but being exposed to ring wraiths is *kinda* a bad trade-off
The name of the thread isn't accurate, but the name of the type is still (), for the same reason that (1u32, 1u32) is of type (u32, u32). So the quote is still accurate.
I think for 90% of the code in the world a language like Haskell is fast enough. For the next 9% Rust with all safety on is fast enough. The next .9% percent can probably be fine with unsafe Rust / plain C. And then there's a few things you basically want to write in optimized C + asm/intrinsics.
at some point everyone learning Rust will bash their head against the borrow checker and ask the Rust gods why their finely handcrafted lifetime annotations fail to pass its muster.