It keeps being a lie
It keeps being a lie
update-in-place when a function consumes a struct and returns a copy of that struct, even with some modifications to the original struct.
The functional programming abstractions are truly zero-cost.
ecency.com/rust-lang/@j...
update-in-place when a function consumes a struct and returns a copy of that struct, even with some modifications to the original struct.
The functional programming abstractions are truly zero-cost.
ecency.com/rust-lang/@j...
Starship is in development.
Government missions fly on the Falcon 9, an operational rocket w/ 99.7% success rate (100% w/ humans aboard).
Musk is not fit for gov’t, but let’s not pretend SpaceX sucks.
Starship is in development.
Government missions fly on the Falcon 9, an operational rocket w/ 99.7% success rate (100% w/ humans aboard).
Musk is not fit for gov’t, but let’s not pretend SpaceX sucks.
I don’t know where this advice came from that ideal thread count = core count (×2 hyperthreads per core). If you’re doing a LOT of file I/O, you might not saturate your CPU until >20 × core count. Experiment and measure.
I don’t know where this advice came from that ideal thread count = core count (×2 hyperthreads per core). If you’re doing a LOT of file I/O, you might not saturate your CPU until >20 × core count. Experiment and measure.
I'm navigating via keyboard due to a wrist injury. It has opened my eyes to the deplorable state of Web accessibility.
We need to do better.
I'm navigating via keyboard due to a wrist injury. It has opened my eyes to the deplorable state of Web accessibility.
We need to do better.