2 ms·
Rust is built to be memory- and thread-safe by default. Assuming you follow the prescribed rules of the language, multithreading is “free”. Amdahl’s Law still
by MontagFTB 2y ago
Rust is built to be memory- and thread-safe by default. Assuming you follow the prescribed rules of the language, multithreading is “free”.
Amdahl’s Law still gets a vote, but at least your app won’t blow up in your face.
- jjtheblunt 2y ago> Assuming you follow the prescribed rules of the language, multithreading is “free”. I'm wondering if you're referring to the async await addition from a few years back, to use of Tokio's crate(s), or something else.
- kevincox 2y agoI think they are referring to this section: https://chevyray.dev/blog/creating-175-fonts/#automatic-kerning https://chevyray.dev/blog/creating-175-fonts/#automatic-kern... In this case they are not using async but Rayon which provides some easy primitives for splitting tasks into smaller parts that can run in parallel. In this case the par_iter and par_extend calls.
- hypeatei 2y agoIIRC, async/await in most languages doesn't imply multi threading, it just allows other work to be done on the same thread simultaneously.