Are we referring to 'go fix' as after market tooling?

It's certainly done in many places. JsDoc is the biggest example I can think of. But they're all walking the line of "this doesn't have an impact, except when it does".

It being done by the language owners just makes them the ones walking the line.

▲

tptacek 10 hours ago | parent [-]

That's exactly how this works: it doesn't have an impact, except when you ask it to. This is an idiomatic approach to this problem.

▲

dwattttt 9 hours ago | parent [-]

The part I object to is overloading comments, which aren't meant to be load bearing. A tool developed outside the language has no choice but to take something that has no meaning and overload it, but language owners weren't forced to take this route; they could've made directives not comments.

In practice, the Go language developers carved syntax out of comments, so that a comment is "anything that starts with //, unless the next characters are go:"

	▲	YesThatTom2 8 hours ago \| parent [-]
		So how many angels can you fit on the head of a pin?