Russ Cox

This program works fine for me (prints StartTLS worked) using a cloud system that can dial port 25 (my home internet gets blocked by my ISP): ``` package main import...

From the discussion so far, it sounds like: 1. Your Mac is configured with IPv6 enabled (that is, IPv6 sockets can be created successfully). 2. Your DNS resolver is responding...

The fix in https://github.com/golang/go/commit/ac08c05d4daa11957fcada6db33f2150936bac27 looks simple enough to backport to me. /cc @matloob @samthanawalla

misc files should not be included in toolchains, full stop. misc is by definition a dumping ground. If there are required supporting files that should be included in toolchains, they...

Even with bad position information it seems like the formatter should understand when it is safe to insert a line break and when it isn't; we should always emit valid...

The similar issues are perfect: #6329 is a related instance of this bug (line number instead of column number), and #56475 was an incorrectly-filed and incorrectly-fixed issue, the fix for...

Note that the compiler does not need a flag to drop position information. Cmd/cover just needs to stop claiming accurate position information in the first place, rolling back the change...

It occurs to me that cmd/compile may now support /\*line x.go:1:2\*/ comments (it did not originally), and so a different fix would be to keep the [CL 446259](https://go.dev/cl/446259) change and...

Ouch, here is a worse error: ``` % cat x.go package p func g() { | func h() { } % go test x.go # command-line-arguments ./x.go:4:1: syntax error: unexpected...

I am running into these because I am running `go test -coverprofile=c.out && uncover c.out` as my testing loop. But I think VSCode Go users would run into these too,...