Band-Aid "go vet" error with Go codegen template

[SeanPMiller]

Resolves #4439

This may not work forever. If it ever stops working, then we can switch to using a const variable, as that is how Rob Pike & Co. intend for debugging-logic to work. Refer to the following issue:

golang/go#16370

[simeonmiteff]

To any fellow travelers wondering how to get this (in lieu of this PR being merged), pipe your generated code through:

  tr '\n' '\f' | \
  sed 's|return localctx\f\tgoto errorExit // Trick to prevent compiler error if the label is not used|if false {\f          goto errorExit // Trick to prevent compiler error if the label is not used\f    }\f    return localctx|g' | \
  tr '\f' '\n'

[SeanPMiller]

Given what a showstopper bug this is for Go developers, I'm surprised it has been languishing unmerged.

[jimidle]

Showstopper? Really? Why would you run go vet on generated code?

[SeanPMiller]

Really. Have you tried to go vet a Go module that depends on another module generated by ANTLR?

[SeanPMiller]

I'll excuse your obnoxious comment.

[jimidle]

Yeah. Sorry - I did not read this correctly. I will add it, but I am just overrun at the moment and have been for a whlie.

[SeanPMiller]

Understood. I've been there. Are y'all short on volunteers?

[vecknishwaran]

Hi, just checking in on the status of this PR. Are there any plans to merge it for now?