Re:Go vgo: Semantic Versioning and Human Error
by weberc2 on Monday May 21, 2018 @08:42PM
(#17122976)
It’s not just public signatures, its also things like types—even private types. For example, if public struct type Foo has a private member of private struct type bar, and private type bar is changed to add a field, this changes the public interface because the memory layout of the type has changed.
[ Parent
| on HN ]
Re:Go vgo: Semantic Versioning and Human Error
by ninkendo on Monday May 21, 2018 @08:51PM
(#17123018)
eh... does this matter though? Go uses static linkage, you have to recompile your code when you update third party libraries anyway.
Re:Go vgo: Semantic Versioning and Human Error
by kasey_junk on Monday May 21, 2018 @09:52PM
(#17123239)
It can cause behavior changes. Especially around memory usage & gc.