3 ms·
> Come back to us when you are on version 3.x, years Someone who has long enough experience in Go would know that the Go compatibility promise[1] only applies
by cratermoon 3y ago
> Come back to us when you are on version 3.x, years
Someone who has long enough experience in Go would know that the Go compatibility promise[1] only applies to Go 1. Go 2 and later are already allowed to break compatibility. I have code I wrote on something like 1.13, if not earlier and it still works fine with 1.20. Sure, there are rare exceptions, but each release documents them.
My question to you, then, is: what exactly did you see in your years of Go experience that broke on a version upgrade?
1 https://go.dev/doc/go1compat#introduction https://go.dev/doc/go1compat#introduction
- pjmlp 3y agoWell, the introduction of new built-ins can bring some surprises into existing code that relies on the same names.