3 ms·
Rust's channel is entirely lock-free. It always was, ever since the first 1.0 release. This is why I think Rust project sometimes has misguided priority. Is ma
by sanxiyn 10y ago
Rust's channel is entirely lock-free. It always was, ever since the first 1.0 release.
This is why I think Rust project sometimes has misguided priority. Is making channel implementation lock-free a good use of pre-1.0 time? Evidently, as shown by Go, lock-free channel is not necessary for wide use, and can be added later. Implementation work should have been deprioritized and probably spent on, say, async IO like Tokio.
- arthursilva 10y agoRust is a much more community driven project, people contribute what they fell like working on mostly.
- sanxiyn 10y agoYou are right in general, but in this case, Rust's lock-free channel implementation and core piece of Tokio (futures-rs) were done by the same person, who was employed by Mozilla when both work was done. So it does reflect Mozilla's priority, not community whim.