rust-x86

This is good for an entirely different reason, which is running cross-compiled tests in an emulator. That is especially good for bare metal. If you don't have global allocator, have limitted ram, etc., you might not be able to write the test harness as part of the guest program at all! so you want want to move as much logic to the host program as possible, and then run as little as a few instructions (!) in the guess program. See https://github.com/gz/rust-x86 for an example of doing some of this.

Ok maybe I was user pointers wrong in Rust. And I must confess that I never really understood lifetimes either, however * I don't think that low level code needs to be "messy", and * I don't think that adding an abstraction on top solves anything complexity wise. For memory paging I used to have a whole library in Rust that handled hierarchy of page tables with very abstract pagetable classes and interfaces [0]. Now I just have 80 lines of zig that handles everything [1]. I much prefer the latter. > I think this is reasonable even for kernel code. It's not, for some of the reasons that Linus doesn't want C++ code in the kernel [2] [0] https://github.com/gz/rust-x86/blob/28d5839933973e0b639ef354... [1] https://git.sr.ht/~jzck/kernel/tree/master/src/arch/x86/pagi... [2] https://yarchive.net/comp/linux/c++.html