News for hackers. Stuff that matters.
Re:Go compiler internals: Adding a new statement to Go by atombender on Friday July 05, 2019 @01:07PM (#20364064)
Unused imports that are imported solely for side effects should be imported this way to avoid that problem:

  import (
    _ "github.com/some/package"
  )
Given that this is the only way to have unused imports with mainline Go — in other words, it's impossible to accidentally remove one once it's been declared this way — I'm not sure I see what the argument is.
Re:Go compiler internals: Adding a new statement to Go by icxa on Friday July 05, 2019 @03:16PM (#20365038)
> I'm not sure I see what the argument is.

That there are other reasons why unused imports are a compilation error in go, and it isn't as simple as turning them into warnings