4 ms·
SemVer itself as a spec expects projects to define exactly what compatibility means, it's true. We went through all of these kinds of cases with Rust, for examp
by steveklabnik 8y ago
SemVer itself as a spec expects projects to define exactly what compatibility means, it's true. We went through all of these kinds of cases with Rust, for example, and defined what kinds of changes increase what kinds of version numbers. Given that it's based on language features, it gives a good basis for the ecosystem, but when you don't have that basis, yeah it's much much tougher.
- int_19h 8y agoIs there any kind of centralized place where "what does semver breaking change means for language X" can be aggregated? I think it can be useful, at least until this is something that language designers routinely include in specs. But there's remains the question of what happens if a library is written in one language, but used from many others with different features that can make non-breaking changes breaking, and vice versa. One could say that the owner of the library is generally not responsible for breaking other languages, but in many cases the library is cross-language by design.
- steveklabnik 8y agoNot currently. Rust has done this, but I'm not aware of other languages having done so.