We are the "thin blue line" that is trying to keep the code high quality

Re:We are the "thin blue line" that is trying to keep the co... by beeflet on Thursday February 13, 2025 @11:11PM (#43044756)

>Bring solutions. Tech debt is just OpEx to everyone else.

What if there was a rust compiler to C, that produced like readable, compliant C code for the kernel. And then developers that want to work in rust can publish their original rust code to some third party location, so the reviewers have no idea if the C code they receive it was originally written in rust or not.

[ Parent | on HN ]

Re:We are the "thin blue line" that is trying to keep the co... by aqueueaqueue on Thursday February 13, 2025 @11:29PM (#43044864)

The output of a compiler produce unidiomatic code. And if the C gets edited you need to back port to Rust which is more work and may be impossible.

Try what you said with even well align languages like TS and JS and it would be hard to work with.

[ Parent | on HN ]

Re:We are the "thin blue line" that is trying to keep the co... by microtherion on Thursday February 13, 2025 @11:26PM (#43044846)

And what happens if somebody starts modifying that C code? Even a one way translator like you describe could be a challenge, making it two way seems close to impossible.

[ Parent | on HN ]

Re:We are the "thin blue line" that is trying to keep the co... by pas on Friday February 14, 2025 @06:36PM (#43054256)

The problem is that the C guys don't want to define certain semantics. Currently "it works", but Rust wants invariants.

[ Parent | on HN ]