Since Resolver is new in 1.8, now is our only chance to get this interface right.

I see there's Dialer.Resolver and net.DefaultResolver; maybe those variables should take an interface instead of a *Resolver? Then you could swap out the implementation that way, without adding anything to the Resolver struct.

It is a concrete type and not an interface on purpose. That lets us extend it with options, like we have with Dialer.

The TODO is about adding an interface or bag of funcs to the Resolver to call first, before the default implementation.

But I'd like to push that off until Go 1.9.

FWIW, I tried working on an implementation of this that would let people override a http.Transport.DialContext. I ran into problems since I wanted to continue to use most of the default DialContext behavior, but it calls a ton of private functions in net (resolveAddrList, dialSerial, dialParallel). I gave up when I got to these functions in fd_poll_runtime.go

// runtimeNano returns the current value of the runtime clock in nanoseconds.
func runtimeNano() int64

func runtime_pollServerInit()
func runtime_pollOpen(fd uintptr) (uintptr, int)
func runtime_pollClose(ctx uintptr)
func runtime_pollWait(ctx uintptr, mode int) int
func runtime_pollWaitCanceled(ctx uintptr, mode int) int
func runtime_pollReset(ctx uintptr, mode int) int
func runtime_pollSetDeadline(ctx uintptr, d int64, mode int)
func runtime_pollUnblock(ctx uintptr)

Is this a dupe of #12503 ?

@kisielk, yes, thanks. I'll close this one.