Comment

A quick “find all references” will point out it’s not used and can be deleted if it accidentally gets checked in but ideally, you have systems in place to not let it get checked into the main branch in the first place.

source

Sort:hotnew top

Flarp@kbin.social ⁨10⁩ ⁨months⁩ ago
Yeah that should be looked for in a CI line check, not a compilation requirement

source
aport@programming.dev ⁨10⁩ ⁨months⁩ ago
You mean a system like the compiler

source
- MJBrune@beehaw.org ⁨10⁩ ⁨months⁩ ago
  Or a linter. Or code reviews. Or anything else. The nice thing is that if the compiler doesn’t demand something. The compiler should have the option to do it. The option could even be defaulted on. Afaik there is no way in Golang to disable that error (this is the line that does it: github.com/golang/go/blob/…/stmt.go#L67-L69). like --no-pedantics or such. Golang’s compiler openly refuses to give engineers more choices in what they think is the best system to handle it.
  
  source
anemoia_one@lemmynsfw.com ⁨10⁩ ⁨months⁩ ago
Yeah any compiler should support environments or confit files. Our CI would never with without –env “stage”

source