Hi Russ, I had a question about this:
> We expect that most developers will prefer to follow the usual “major
branch” convention, in which different major versions live in different
branches. In this case, the root directory in a v2 branch would have a
go.mod indicating v2, like this:
It seems
I agree on the getting the experience right for Go users piece and I think
that we both see our views as in line with that theory. I think having less
surprising, less gotchas and less defaults-gone-wrong behavior is better
than enabling things that will get in their way and cost them developmen
There's two features that are in Go 1.10 that are opt-out new defaults. I
sincerely apologize for not being active enough to spot them before now.
> The go test command now caches test results: if the test executable and
command line match a previous run and the files and environment variables