-
Is Rust allowed for the development of some parts of the kernel? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hello! This is definitively an interesting question. For Tilck, the biggest problem with Rust is the toolchain: I spent quite some time working on the Even if there was something like pre-compiled toolchains for each architecture for Rust, it will require an significant amount of time to integrate all of that in Tilck. Realistically, supporting Rust would mean adding an extra step to download and locally build the cross-compiler toolchain, in addition to all the rest (e.g. build-system integration, creation of Rust definitions of structures etc.). I don't plan to work on the Rust support any time soon, especially because I have a full-time job that keeps be super-busy. But, in the very long term (years) I might add support for Rust in the above-described way and probably start porting some of the more high-level code into it. I recognize that many younger developers will totally appreciate that. |
Beta Was this translation helpful? Give feedback.
Hello! This is definitively an interesting question.
When I start developing Tilck in 2016, Rust was barely just born and it didn't make any sense to use it. Now, everything is different and Rust is entering in the Linux kernel too. Therefore, Rust seems to be a valid language for low-level code.
For Tilck, the biggest problem with Rust is the toolchain: I spent quite some time working on the
build_toolchain
script and on Tilck's CMake-based build system in order to allow switching easily between multiple pre-built GCC toolchains (from toolchains.bootlin.com), even across architectures. For Rust there is nothing exactly like that yet. Linux doesn't care about such things because the whole…