On 12/27/13 1:34 PM, Daniel Micay wrote:
On Fri, Dec 27, 2013 at 4:29 PM, Tony Arcieri <[email protected]> wrote:
On Thu, Dec 26, 2013 at 6:29 PM, Nathan Myers <[email protected]> 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.
I think the standard library should get there over time though.
Patrick
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
