News for hackers. Stuff that matters.
Re:Curry-Howard, the Ontological Ultimate by AnimalMuppet on Wednesday October 15, 2014 @01:33PM (#8460140)
Let's go further. If I'm writing, say, numerical calculations, types can save me from getting kilometers when I expect miles (or, worse, kilograms). What it can't do is save me from numerical instability, round off errors, and a whole host of other problems known to the field of numerical analysis.

If my code is calculating the angle of a control surface on a plane, the type system is not going to say anything about whether I get 40 results every second. Without those constant, timely updates, the plane is going to crash.

A robust type system means that "your code is correct by construction"? That seems incredibly naive. There's more ways for programs to be wrong than are provable via a type system.

Re:Curry-Howard, the Ontological Ultimate by Confusion on Wednesday October 15, 2014 @04:10PM (#8461401)
Concerning 'numerical instability': with a sufficiently advanced type system you should be able to save yourself from something like numerical instability. You could e.g. ensure all numbers have an 'order of magnitude type' and define operations between 'order of magnitude' types to raise errors for certain (ranges of) combinations. However, there is (AFAIK) no convenient way to express this in any language, let alone without performance suffering greatly.