Ok, so maybe they should be disabled by default. But to eliminate them outright would be shortsighted, IMHO. Can we leave them as an option for people who do care about this sort of stuff?
On Mon, Oct 21, 2013 at 8:48 PM, Daniel Micay <danielmi...@gmail.com> wrote: > On Mon, Oct 21, 2013 at 9:57 PM, Vadim <vadi...@gmail.com> wrote: > >> Hi Brian, >> Can you please elaborate on why segmented stacks fell out of favor? >> Maybe it's been discussed among the core Rust team, but external people >> like me are probably wondering why. >> It seems to me that segmented stacks would be essential for async I/O and >> actor-based architectures, no? >> >> Vadim >> > > Segmented stacks result in extra code being added to every function, loss > of memory locality, high overhead for calls into C and unpredictable > performance hits due to segment thrashing. > > They do seem important for making the paradigm of one task per connection > viable for servers, but it's hard to balance that with other needs. >
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
