Re:What's next for SemVer
by steveklabnik on Monday February 11, 2019 @05:10PM
(#19138861)
SemVer talks a lot about compatibility, but doesn't define it. Each project is supposed to on its own. You can just say this for any given project, and it would be compatible.
[ Parent
| on HN ]
Re:What's next for SemVer
by slowmovintarget on Monday February 11, 2019 @10:52PM
(#19140891)
I prefer Rich Hickey's definition of compatibility [1]:
A function is compatible if it requires no more than it did, and provides no less than it did in the previous version. A library is compatible if it provides no fewer functions, and requires no additional context (transitive dependencies) to use it, and all of its functions are compatible as defined.
When you wish to require more, or provide less, you make a function with a new name.
[1] As linked elsewhere: https://youtu.be/oyLBGkS5ICk?t=1189