That sounds about right, yes. (That's just not the scheduler that exists now. And this is the first I've heard of the idea that Rust might get such a scheduler, although it seems like a useful thing to have.)
Glenn On Oct 24, 2012, at 9:13 AM, Lucian Branescu wrote: > 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:508813b1235362133512636! >
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
