5 ms·
I mean the `+incompatible` gets added there for a reason, it's not doing it "blindly" because it "doesn't understand" it. You might not like what what go toolin
by morelisp 6y ago
I mean the `+incompatible` gets added there for a reason, it's not doing it "blindly" because it "doesn't understand" it. You might not like what what go tooling does with its semver awareness, but it is semver-aware.
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- Groxx 6y agoIt's not incompatible with semver though, it's just incompatible with Go's "semver is folders". Go's "semver" is full of weird corners. E.g. if you tag v1.2.3 and then someone does a `go get ...@master`, they get "version" `v1.2.4-timestamp-gitsha`. `v1.2.4` doesn't exist anywhere, Go just makes it up: https://golang.org/ref/mod#pseudo-versions https://golang.org/ref/mod#pseudo-versions . It works for their system with minimal changes, and is thus a clever hack, but it's definitely weird.