Take C. Add a slice construction to replace manual length annotations. Add option typing to replace NULL. Add lifetimes and a borrow checker. Add a separation of safe vs unsafe with an explicit annotation for the latter. Oh wait maybe we should just use Rust.
-
-
-
It's kind of like saying "what we really need is Rust but without all those productivity features that make it actually enjoyable to write code".
- 3 more replies
New conversation -
-
-
Memory safe C is C!... assuming a developer who can internalize all places where UB happens in C
-
And retain and recall all of the memory- and lifetime- invariants of every line of code in the current project and all of the libraries it references...
- 1 more reply
New conversation -
-
-
Just don’t write bugs in your code. It’s that easy.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Your response is slightly more generous than mine.https://twitter.com/khuey_/status/1190057956378693632 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I can't believe nobody thought of that before!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
it's simple, we just force every C programmer to also produce a proof of memory safety for every program! That'll be easy, right?
-
now if you'll excuse me i need to finish my 600 line proof that says I'm allowed to rename variables in programs
End of conversation
New conversation -
-
-
Rob lives to be trolled by me, but I show mercy here.
-
Takes one to know one. I’ll let you guess if I’m referring to your tweet or mine
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.