Unnecessary Optimization in Rust: Hamming Distances, SIMD, and Auto-Vectorization
https://programming.dev/post/23203836
=> More informations about this toot | View the thread
Zero Bugs
https://programming.dev/post/23068539
=> More informations about this toot | View the thread
Singletons in JavaScript
https://programming.dev/post/21537179
=> More informations about this toot | View the thread
Feds: Critical Software Must Drop C/C++ by 2026 or Face Risk
https://programming.dev/post/21219428
=> More informations about this toot | View the thread
I was aware that indeed the trait and lifetime bounds were an artifact of the Tokio work-stealing behavior, but Evan makes a very well-explained case for why we might want to consider stepping away from such behavior as a default in Rust. If anything, it makes me thankful the Rust team is taking a slow-and-steady approach to the whole async thing instead of just making Tokio part of the standard library as some have wished for. Hopefully this gets the consideration it deserves and we all end up with a more ergonomic solution in the end.
=> More informations about this toot | View the thread
Async Rust can be a pleasure to work with (without Send + Sync + 'static
)
https://programming.dev/post/19010984
=> More informations about this toot | View the thread
Biome v1.7
https://programming.dev/post/12807878
=> More informations about this toot | View the thread
Rust Optimization: Vec::into_iter().collect()
https://programming.dev/post/12598716
=> More informations about this toot | View the thread
Productivity of Rust teams at Google
https://programming.dev/post/12036286
=> More informations about this toot | View the thread
Unused lifetime parameter -- except it isn't
https://programming.dev/post/11838278
=> More informations about this toot | View the thread
=> This profile with reblog | Go to arendjr@programming.dev account This content has been proxied by September (ba2dc).Proxy Information
text/gemini