3 ms·
They are not just addressable, but actually make Rust itself a better systems programming language.
by xiphias2 6y ago
They are not just addressable, but actually make Rust itself a better systems programming language.
- steveklabnik 6y agoYes, I specifically would really like to see what Josh is talking about here happen: https://lore.kernel.org/lkml/YHdSATy9am21Tj4Z@localhost/ https://lore.kernel.org/lkml/YHdSATy9am21Tj4Z@localhost/ It's kind of a funny space; right now Rust handily gives you "no allocations" (this is where I live) or "infallible + fallible allocations" (this is alloc/std by default) but not "only fallible allocations". This sort of thing is basically filling out the quadrant of options.
- hathawsh 6y agoThe most impressive part is that it's actually conceivable to implement such deep changes without a major version bump in Rust. (I hope so anyway!)
- steveklabnik 6y agoYup, it is. If this plan linked above were to be implemented, what would happen is that you would get the same behaviors by default, but with a new setting, you'd get some APIs removed. That's backwards compatible.
- tetha 6y agoI was thinking that when reading the exchanges. This is a really good interaction. Linus and the kernel have strong requirements for good reasons, and the rust teams are trying to address them in useful ways. Rust in the kernel is not a simple thing, but I think both rust and the kernel will benefit.