Brad Fitzpatrick

Would using latest active LTS be sufficient for you? Otherwise let's just ignore nodejs for our wasm policy reasons. Nodejs people with a few servers can update. Millions of end...

We just updated our builders from nodejs v8.11.1 to nodejs v12.1.0 for #31282 But I continue to believe that Linux distros' current version of nodejs doesn't matter at all. Our...

Let's ignore ReverseProxy for the purpose of this bug. Although, ReverseProxy being in std would require that new API be added to net/http.Client. I think more immediately we'd want to...

@snadrus, what does grpc have to do with PUSH_PROMISE? I see nothing in http://www.grpc.io/docs/guides/wire.html

@brunomcustodio, zero chance. There's not even code, and also https://golang.org/wiki/Go-Release-Cycle

Nope.

What about letting `return` take 1 thing regardless of how many results the func has, as long as the assignment is unambiguous to exactly 1 of the return types? So:...

> It would also be unusable with interface{}, though that's a bit niche. That's a feature.

I think it'd be nice to have three unspecified, though. Because once we add `netaddr.ParseIPPort` (for the newly added `IPPort` type), then we'd want `ParseIPPort(":80")` to have an IP that...

@danderson, the general solution to that is canonicalization methods for those who need it. (e.g. https://golang.org/pkg/time/#Time.UTC and https://godoc.org/inet.af/netaddr#IP.Unmap) @mdlayher, > Would var ip netaddr.IP then imply "dual-stack unspecified IP address"?...