I think you'd get back the same situation as in C with a scheduler that ran each task in its own thread, or at least that's what I was told.
On 24 October 2012 16:58, Glenn Willen <[email protected]> wrote: > Well, it's worse than that I think? You will have far more than the usual > problems of blocking I/O, because the Rust scheduler will be unaware of your > blocking, and will not be able to switch tasks when you block. So if you have > multiple tasks, blocking I/O will break everything. > > Glenn > >> Rust will (and already does) support blocking IO, it just won't try to >> automatically make it look non-blocking (like Go does). >> So you can use sockets if you wish, but you have all the usual >> problems of blocking IO. >> _______________________________________________ >> Rust-dev mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/rust-dev >> >> >> !DSPAM:5087b8fa307329028381310! >> > _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
