On Fri, Dec 27, 2013 at 4:29 PM, Tony Arcieri <basc...@gmail.com> wrote: > On Thu, Dec 26, 2013 at 6:29 PM, Nathan Myers <n...@cantrip.org> wrote: >> >> A systems language meant to implement rigorously specified >> designs needs to be as rigorously specified itself -- a huge job, >> at best. For that, it needs a primitive with behavior that can >> be completely and precisely expressed for all runtime conditions. > > > This is an excellent point, thank you! > > So here's a big question: if Rust tasks and channels were the underpinnings > of an operating system kernel, would unbounded channels be suitable or not? > > -- > Tony Arcieri
Rust tasks and channels don't work in a freestanding environment. Unbounded allocation is *definitely* not suitable for a kernel though... even a large bounded channel would be unsuitable. The world of small stacks and interrupts is quite different than what the standard library is written for. _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
