Viewing profile — rogpeppe1

One of Go's big selling points is the avoidance of the "red-blue problem" ( https://journal.stuffwithstuff.com/2015/02/01/what-color-is-... ). The standard Go implementation does t…

> Sure, but more data will be attached to it. Also, in his proposal, he said that IP addresses will not be logged. I seriously doubt that. I think it's worth quoting what Russ said…

> First, making network requests when downloading packages is necessary for the tool to function and unavoidable. It's technically not unavoidable. The Go authors could have made u…

So you see this as just the same, from a privacy perspective, as the way that the Go tool already dials out to the Go proxy by default? That is, if you're OK with that (I'd assume …

Have you read the articles? How is this in any way violating privacy?

> @rsc, if you ever see this, your proposal here means that I will never use any software written in Go ever again, if at all possible. Have you actually read the articles? The "da…

That ship has already sailed. The Go tool already by default makes network requests to the Go proxy, which potentially allows everything that you're talking about there. What's sig…

I'm not sure that hiding the implementation is worth it here. Why not just make it public that it's actually map[T]struct{} underneath - then anyone can range on it and implement a…

There's no need to use the pointer in there; you could just use an ok bool instead (saving the indirection): https://go2goplay.golang.org/p/4hr8zINfRym I think it's interesting to …

OK, replying to myself for future reference. I found the answer here: https://youtu.be/0GeJdTTzaDo (incidentally, that series of videos seems to have solutions for most of these pr…

This was a fun puzzle, but I came to a roadblock here too. I have to confess I'm confused by what I believe might be the "local hypothesis block" mentioned above. The confusion is …

You can specify that a given dependency be replaced by another one. That only applies at the top level though, not when the go.mod file with the replace clause is used by another m…

Don't keep type safety then. Think of Go as half-way between Python and Haskell in that respect. Types are great when they're useful, but they're not required .

I tend to check out one branch, run godeps -u, then check out the other one and run godeps -N -u. Then you've got the newest deps from both branches. I still wouldn't resolve the c…

> I'd rather have a test that correctly reasonably verifies that a package is correct (or at least "passes the race detector consistently") and reaches into some of the private det…

> Mocking out the time functions means you don't get any race conditions. This is a common misapprehension. Actually, even if you fully mock out time, you can still get race condit…

The godeps file is just a dependency-per-line, tab-separated values, deliberately so it's easily amenable to shell script processing. Aside: the conflicts mentioned in the article …

Exceptions don't always give you useful stack traces in a concurrent situation, because the current stack may only reflect a goroutine that's processing data on behalf of another. …

or gopkg.in/errgo.v1 which is a bit more opinionated about error causes.

This particular issue is unfortunate - it can't be changed without potentially breaking existing programs. See https://github.com/golang/go/issues/11513 and https://groups.google.c…

From the article: In order to do evil things like convert raw bytes to floats, I chose to use the “unsafe” package FWIW you don't need unsafe to do that. encoding/binary + http://g…

I'd like to hear more details of your issues here. What's not good about the bufio package? What do you mean by "poor abstractions"? What's wrong with creating a single purpose loc…

FWIW Go does implement a significant subset of generics in a type-safe way. For any parametric type P[T], if P has no public methods or fields that mention T, then Go can implement…