based on this ridiculous claim, I posit that you have never tried to design a usable language starting with a formal model
-
-
-
I suspect there's some gap between the levels of formality we demand to call something a formal model.
-
I don't care that it look like something out of a formal logic textbook that spends ridiculous effort proving the obvious.
-
But a language that lacks a fairly rigorous specification that's at least theoretically formalizable is a huge mess.
-
"Design by implementation and worry about a spec later" can work out, eventually, but usually it doesn't...
-
...and leads either to dead-end languages that can never have more than one implementation (Perl) or compat hell (JS, oldschool C, ...).
-
conversely, what you describe here is just Rust's RFC process, and it's overall not particularly remarkable.
End of conversation
New conversation -
-
-
It was (and arguably still is, though increasingly not) an open problem to design a formal model supporting everything unsafe Rust supports.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.