3 ms·
In practice that's very not true. Plenty of room for undefined behavior in statically typed languages like Java, C# etc.
by bird_monster 6y ago
In practice that's very not true. Plenty of room for undefined behavior in statically typed languages like Java, C# etc.
- kingdomcome50 6y agoOf course there is. That's not my point.
- bird_monster 6y ago??? You literally posted that using a statically typed language prevented breaking changes?
- kingdomcome50 6y agoDid I literally post that? You might want to reread my comment. I can say from experience for every language above, save C++ (with which I have never worked), that they will fail to compile if you change a function signature in a backwards-incompatible way and fail to update all call sites. The purpose of static typing as a method of program verification is to enforce type constraints at compile-time for all possible executions of that program. A function signature is, you guessed it, a type constraint.