[stevebmark]

It does sound painful to have to update a package version by updating an import string in hundreds of files

[klodolph]

It is not painful in Go.

For example… let’s say you have just plain search-replace and no smart tools. You need to update github.com/abc/def to github.com/abc/def/v2. This is a search-replace operation.

This only happens when packages publish breaking changes. The minor version is stored in go.mod.

[earthboundkid]

You can do it using gofmt, by writing

gofmt -w -r '"github.com/abc/def" -> "github.com/abc/def/v2"' .

That won't do subpackages though.

[nolok]

Now add complex versionning and optional dependancy and dev level dependancy and... You'll get what he means.

Every language starts the way you describe, then needs are added.

[klodolph]

I’ve been a Go programmer for many years now, and I don’t “get what he means”. Am I stupid? Maybe you could elaborate.

What is complex versioning? In Go, you specify a minimum minor version, and breaking changes change the package name & import path (or they’re supposed to). Why would I want complex versioning? The underlying problem that versioning solves is complicated, but that doesn’t mean you benefit from a complex versioning scheme.

[pavlov]

#define SDK_VER 1.2.3