On Friday, August 31, 2018 at 12:22:28 PM UTC-5, Victor wrote:
>
> Hello everyone. I'm looking for best practices on how to setup your
> development environment using Go modules.
>
> Let assume a situation when you work on a project where you write a go
> package (call it Pkg) and an applicatio
`go.mod.local` was one idea. Another idea is to have a sort of "publish
local" semantics, where the go tool has support for something like
-devel tags, which override the defined in go.mod. So
then you would "publish" the next version to your local mod cache (just
creating/updating the module
> The question is what to do with /r/golang when all moderators of it want to
> leave.
/r/golang was founded by a non Googler, non Go team member. The subreddit was
fine before you guys took over. It'll be fine if you leave. There is a pretty
clear precedent set by the Go project for community
https://github.com/shoenig/test
We've been using this for a couple years now, and it's been great. I am
biased though, for obvious reasons. It makes use of the go-cmp library
under the hood for creating legible diffs, and integrates well with
protocmp for when you need to work with protobufs.
