6 ms·
No, actually that was just javascript. Programming environments with threading models don't have to live that way. Separate threads can communicate through chan
by jeremyjh 3y ago
No, actually that was just javascript. Programming environments with threading models don't have to live that way. Separate threads can communicate through channels and do quite well for themselves. See how it works is, you do something like let data = file.read(); and the it just sits there on that line until the read is done and then your data has the actual bytes in it and you just use them and go on with your life.
- eklavya 3y agoMaybe you are both right but your scales are orders of magnitude apart.
- zozbot234 3y ago> you do something like let data = file.read(); and the it just sits there on that line until the read is done and then your data has the actual bytes in it and you just use them and go on with your life. That's exactly how async/await works, except that it translates to state machines under the hood which gives you great performance. No need to mess with threading models, at all.
- vacuity 3y agoYeah, Rust's async/await and lightweight threads are functionally very similar. Function coloring is a problem with async/awaitt, though (for now?).
- iudqnolq 3y agoUntil you need cancellation
- ragall 3y agoOne rarely really needs that.