On Tue, Jul 7, 2020 at 2:56 AM Amnon <amno...@gmail.com> wrote: > A sensible, well thought out, design. > > My main worry is that we will come unstack in places that are using > versions of the Go toolchain older than N-2. > Is there any reason for them not to upgrade? No > Should they upgrade? Definitely > But some still haven't. > > Perhaps we should force them to upgrade to a supported version. > Perhaps we should say that if they don't upgrade, then any pain they > suffer will be their own fault. > But these are decisions that we must consciously take. >
For what it's worth, they need not ever upgrade as long as they keep running old Go code. If they do upgrade to newer Go code without also upgrading the Go distribution, there is already the possibility of build breakage due to the new code making use of new standard library functions (breakage = undefined symbols) or language features (breakage = syntax or type error). The new //go:build lines are not that much different: if they are present alone in a file and are not respected, you get a break, not silently wrong behavior (brekage = duplicate definitions for a symbol, almost always). Best, Russ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAA8EjDQz0Emxc0_OnxLzXw1MybW3Ni17V%3Do8P4we7DVQ9yokfA%40mail.gmail.com.
