Tim Heckman

@krak3n I think this could be an interesting idea, but before expanding the API I'd love to understand how these errors could be handled. At least for the one provided,...

@rburmorrison I'll start by saying I'm a proponent of `cmd/`, especially when you have multiple binaries being built. It gives you a good starting point to understand how the library...

@kcq I'm speaking in terms of what has become a general consensus in the Go Slack and Forums areas. The Go authors themselves have been absent in providing guidance on...

@hron84 In Go you can put it at the top level of a package so all things inside of that repository can use it. If you are looking for code...

@peterbourgon It's not clear and unambiguous to me, because it's honestly not clear what value it adds beyond cognitive overhead and unnecessary abstractions. To me it's just noise. I don't...

Hmm, that makes me less convinced. If I'm looking for Go code I generally have an entry point. A function, a file, some string to search for, etc. I use...

I am 100% aligned with both @rsc and @rakyll on their comments. We experience the same misconception about the status of this repository in the Slack workspace, especially for those...

I am not sure we can assume the user's intent when they star a project. I know for many it signals an interest to understand or explore a project later....

@xhit considering we have `go fmt` to consistently style source code, I could see some then wanting or even expecting to find a style to use consistently to structure their...

@ymherklotz I'm not personally experiencing this, but have experienced similar things before when my shell was slow to start because of junk I had in my `.zshrc` file. That isn't...