How are they going to tackle heavy use of the C preprocessor?
What about pointer arithmetic without decorating everything with “unsafe”? As the whole point is making the code safer.
Can’t have code vulnerabilities if the code doesn’t run. *taps forehead*
I guess it will translate the majority of the code which does not contain unsafe parts, and leave the pointer manipulation for manual rewrite.
Or maybe it’ll write the unsafe parts in unsafe blocks?
Then there’s no point. Converting the code to Rust as-is will also transfer all the bugs.
There is. It’s a starting point to start converting the code to safe Rust. Some obstacles are removed.
you can just wrap a whole C code into a macroyeah, preprocessor is going to blow everything, I forgot how good it is. Maybe there’s a way by preprocessing and then leaving it as the code, but that wouldn’t be as useful and configurable
Can’t spell CVE without C 😉
No wonder security aware environments want to get rid of the language. It’s a mess and a half (can’t forget the buffer overflow).
However the suggestion of using AI kinda voids the proposal and erodes credibility.
Can’t spell CVE without C. It’s a mess and a half (can’t forget the buffer overflow).
I’m saving these, folks are gonna love them lmao.