There's a legitimate debate as to how much Rust would benefit the core memory manager, scheduler, etc. But the benefits to drivers are obvious.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Drivers are one area of attack but I'd also look at the kernel/user-space interface. Could Rust's type system be used to check that the kernel is accessing user pointers in a safe way?
-
Yes, I’m pretty sure it could, and that’s a really good point.
End of conversation
New conversation -
-
-
Reminds me of
@qDot's vision of all Firefox hardware code being in RustThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I'd pull up the spec for a common controller interface like xHCI or AHCI and think about how you'd write a driver for that in Rust. I'm curious what kinds of primitives you'd build for manipulating what is essentially a shared memory data structure.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
fwiw, i wrote a scheduler + message passing interface w/ rust to teach myself how to code in it. i would love to see someone who knew what they were doing do Rust/L4.
- 2 more replies
New conversation -
-
-
I've never written any unsafe code, so a legitimate question: How inconvenient does rust make it to write unsafe code? Are there things beyond putting code in an unsafe block that get in the way?
-
I wouldn't say inconvenient - rather that it makes you uncomfortable about having it in your src and rethink your code structure. Personally, i have yet to write unsafe code which i didn't replace with safe before shipping (except for bindings)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.