Josh Bleecher Snyder

> @josharian's github.com/josharian/native that he mentioned in https://github.com/golang/go/issues/35398#issuecomment-675015994 is closest, but lacks the constant that we ended up needing in Tailscale. FWIW, I know the author of that package, and...

@DeedleFake the compiler only coalesces byte-by-byte memory reads/writes if it knows that it is safe to do so, based on the architecture, alignment, whatnot. The unsafe version says to the...

I believe that we could avoid duplicating the full implementation with a touch of embedding: ```go var NativeEndian nativeEndian type nativeEndian struct { littleEndian // or bigEndian } ```

And just to throw out more ideas...another option for exposing a useful constant directly via encoding/binary could be to give nativeEndian (and bigEndian and littleEndian?) an `IsLittleEndian`/`IsLittle` method that returns...

@stephens2424 seems promising. If it isn't too much work, please do mail a CL.

And I want this, but I do want the test binary. I'd use it to compile tests, change the compiler, compile tests again, and then run before/after benchmarks. (All in...

What if we leave that up to the user to diagnose? If package A's test interferes with package B's use of package A, then don't test them together. This sort...

They'll know when the test fails. If the tests pass when run independently (i.e. `go test ./...`, no `-c`), then there's clearly an interaction problem.

I can't imagine someone wanting to run `go test -c ./...` on their entire GOPATH unless they had a very good reason. I can, however, see this for a particular...

> How many packages support go test -count=2? Even some of the std packages don't, until they're > fixed not long ago. Exactly. And they got fixed because people cared....