News for hackers. Stuff that matters.
Re:RustBelt: securing the foundations of the Rust programmin... by phkahler on Sunday February 04, 2018 @02:19PM (#16304306)
But "this language is hard to verify" should not trump the usability of the language. The verification only needs to be done once, while the language will be used to write code again and again. If it doesn't negatively affect the language users then sure, change it to make verification easier.
Re:RustBelt: securing the foundations of the Rust programmin... by emn13 on Sunday February 04, 2018 @04:57PM (#16305171)
You're not verifying a language, you're verifying a program (or some part of one). Sure- that part in this instance may be implementing a language standard library, but who cares? That program also has tests, docs, types and all the other things people use to convince themselves of correctness.

It really is like unit testing. There too you could make the argument that in some cases untestable code might be worth it if the alternative is an api that's hard to use. And there too an api may well be used many orders of magnitudes more frequently than it is changed. I think you have to decide that on a case by case basis (at least, I can't think of any convincing general argument there).

Re:RustBelt: securing the foundations of the Rust programmin... by monocasa on Sunday February 04, 2018 @02:28PM (#16304366)
You need to reverify when you change the code too. Otherwise you could make the same arguments about testable code.
Re:RustBelt: securing the foundations of the Rust programmin... by nine_k on Sunday February 04, 2018 @02:43PM (#16304477)
It depends on the cost of a defect. A language used for aircraft control software is going to have much stricter requirements for static analysis that a language used to create a website with cute pictures of kittens — even if happens to be the very same language.