|
| ▲ | JoshTriplett an hour ago | parent | next [-] |
| > Platform support being the big one. And between rustc_codegen_gcc, projects like https://github.com/FractalFir/crustc, the ongoing addition of backends to LLVM and Rust, and the eventual removal of obsolete targets as hardware goes away, that's less and less of a problem. |
| |
|
| ▲ | xedrac an hour ago | parent | prev | next [-] |
| Since the Rust support in the kernel is not optional, it already has an impact on platform support, no? Or maybe they are using the gnu toolchain to avoid that? |
| |
| ▲ | JoshTriplett an hour ago | parent [-] | | Rust support in the kernel is still optional; it's currently only allowed in drivers, and drivers only use Rust if they can accept running only on current Rust targets (which is not a substantive limitation). I expect Rust to eventually get used in the core kernel, or in drivers that everyone wants to use (e.g. some new bus or device on most new hardware), but I expect that by the time that happens the set of targets supported by the kernel and the set of targets supported by Rust (including through things like crustc and codegen_gcc) will have converged sufficiently. |
|
|
| ▲ | lioeters 2 hours ago | parent | prev [-] |
| [dead] |