[Canonical-tech] Handling active dependencies in Go

[roger peppe]

On 22 December 2012 08:22, John Arbash Meinel <john.meinel at canonical.com> wrote:
> We can work around it, by being disciplined as a library developer.
> You still have the state where the code using the library only builds
> because the library didn't accidentally commit a change that broke things.

Forgive me for not being familiar with more usual versioning systems,
but wouldn't that be true in other systems too, if you commit a change
that modifies an existing version?