4 ms·
With strong typing, you can analyze the code and automatically increment the semver versions based on public API changes. Elm does this AFAIK. Reduces the amo
by woolvalley 9y ago
With strong typing, you can analyze the code and automatically increment the semver versions based on public API changes. Elm does this AFAIK. Reduces the amount of mistakes that are possible.
- dragonwriter 9y ago> With strong typing, you can analyze the code and automatically increment the semver versions based on public API changes. This is nice, but should be noted does not absolutely prevent missing backward-incompatible changes; that a function has the same signature does not mean that it has backward compatible behavior. (With a rich enough strong, static type system, used well to start with, you might hope that all meaningful behavior changes would manifest as type changes as well, but I don't think its clear that that would actually be the case even in a perfect world, and in any case, its unlikely to be the case in real use even if it would be in the ideal case.)
- steveklabnik 9y agoYup, elm pioneered this space. We're giving it a shot too https://github.com/rust-lang-nursery/rust-semverver https://github.com/rust-lang-nursery/rust-semverver