> It's a complete non-issue. It is an issue as someone who doesn't write Go code often but occasionally reads/debugs it. At least for the first couple of times

> It's a complete non-issue. It is an issue as someone who doesn't write Go code often but occasionally reads/debugs it. At least for the first couple of times I've come across it made me scratch my head for a couple of hours, because I didn't see what the issue was it being 'hidden' in the comments. Which is fine. It just isn't in line with the general premise of Go's language design, so I wasn't even expecting it. So in a sense you are right!