3 ms·
An unmaintained package doesn't need new features from then-future versions of Go, so it's fine if you declare the current version as your max. It doesn't break
by chc 8y ago
An unmaintained package doesn't need new features from then-future versions of Go, so it's fine if you declare the current version as your max. It doesn't break in the new version, it just doesn't have access to features introduced after the max version.
- cortesoft 8y agoWon't you then lose out on performance improvements that don't break your code.
- ithkuil 8y agoversion of the language spec != version of the compiler I.e. future compilers can understand previous version of the language spec.
- chc 8y agoAs outlined in the proposal, you wouldn't miss out on performance improvements since it would still be the same underlying compiler and the version just controls the syntax rules. (And even if that were the case, it's not a very bad worst-case scenario for an abandoned project.)