3 ms·
> Despite my strong attachment to the Rust community and Rust’s perfect suitability for kernels1, I’ll be writing the kernel in C. Mostly because it
by shmerl 10y ago
> Despite my strong attachment to the Rust community and Rust’s perfect suitability for kernels1, I’ll be writing the kernel in C. Mostly because it is unlikely people inside the university will be familiar with Rust, but also because GNU-EFI is a C library and I cannot be bothered to bind it. I’d surely be writing it in Rust were I more serious about the project.
I saw an example of booting from UEFI in Rust: http://blog.theincredibleholk.org/blog/2013/11/18/booting-to-rust/ http://blog.theincredibleholk.org/blog/2013/11/18/booting-to...
- hornetblack 10y agoThis is quite an old version of rust[1]. I tried this a little while ago (but got frustrated trying to link it) [1] For example: * `u16` would now be: `const u16` * `int` is no longer a type. * `slice::as_ptr` is now a method, so using transmute to extract the pointer from a slice is probably not ideal. * `core` is a crate that includes things like transmute so you don't need to manually include rust intrinsics etc.
- shmerl 10y agoYes, it's obviously somewhat outdated, since it's from 2013, which was before the first release.