Re:Hard Rust requirements from May onward for all Debian ports
by OptionOfT on Saturday November 01, 2025 @12:11PM
(#45782808)
What is the concern with LLVM? I'm asking because I genuinely don't know.
[ Parent
| on HN ]
Re:Hard Rust requirements from May onward for all Debian ports
by wolvesechoes on Saturday November 01, 2025 @12:28PM
(#45782973)
I would assume that because it is written in unsafe C++, it creates technical debt that should addressed rather soon.
Re:Hard Rust requirements from May onward for all Debian ports
by smithkl42 on Saturday November 01, 2025 @12:32PM
(#45782996)
I think the issue he's pointing at is that LLVM is itself written in C++ - so the entire "trusted" Rust toolchain depends on trusting a huge C++ app.
Re:Hard Rust requirements from May onward for all Debian ports
by vlovich123 on Saturday November 01, 2025 @01:55PM
(#45783759)
Thankfully the “trust” you need out of a compiler is very very different. It would be closer to claiming you need to compile it on a Rust OS too because you’re trusting a large C/C++ app.
Separation of concerns solves this because the compiler has minimal impact on the trustedness of the code the Rust compiler generates. Indeed, one would expect that all the ways that the LLVM compiler fails are ways any Rust implementation would fail too - by generating the wrong code which is rarely if ever due to memory safety or thread safety issues. There may be other reasons to write the compiler backend in Rust but I wouldn’t put the trust of compiled Rust code as anywhere near the top of reasons to do that.