3 ms·

The bug was introduced in Go 1.5 (when the compiler was rewritten to Go)

• mseepgood 10y ago
  No, it was introduced in Go 1.4, when the runtime was rewritten in Go.