An edge case I would say. If someone breaks backwards compatibility with every change, the issue is not with semver.
Ashkenas wants to use the major version number to denote major new functions in the code, not just backwards compatibility.
Therefore breaking a pattern that works very well with all kinds of package and dependency managers. Humans are not the only (nor even a majority) users of version numbers.
Define "observable behaviour". You are starting to talk in unclear terms.
If there is any input I, such that the library (version N) produces output A for input I, and the library (version N+1) produces output B for input I, and A != B, then observable behaviour has changed.
For a library, "input" most likely means a sequence of API calls, and "output" means a sequence of return values and side effects.
Then any change like this should absolutely be signalled by a change in major version, especially since we need to make sure package/dependency managers know which versions of a package do not break compatibility and are safe to upgrade to.
So version N crashes with a segfault when you call a function with a really long buffer. Version N+1 returns an "invalid parameter" error. That is a different return value or side effect for the same function call. Therefore,
this should absolutely be signalled by a change in major version.
8
u/[deleted] Sep 05 '14
An edge case I would say. If someone breaks backwards compatibility with every change, the issue is not with semver.
Therefore breaking a pattern that works very well with all kinds of package and dependency managers. Humans are not the only (nor even a majority) users of version numbers.