> If you look closely, those aren't angle brackets, they're characters from the Canadian Aboriginal Syllabics block, which are allowed in Go identifiers. From Go's perspective, that's just one long identifier.
And the next comment is the same thing everyone else is thinking: “oh my god”
Gives new meaning to the phrase "Native apps"From Go's perspective, that's just one long identifier.
The designer was using those characters to trick the Go compiler which I then suspect means things like go format would also continue to work.
Then the designer could easily create a pre-processor that translates those placeholders characters as a way of providing some sort of generics in Go.
So in reality this was quite a good solution as I can imagine coming up with a solution that broke go format would have been a real pain to use.
Yes, I do not understand why people find this so hilarious. It's a clever choice.
Here is __REPLACE__ var.A wise choice would be simply adding double underscores between the identifiers.
> c++ allows 0-width spaces in variable names. Where's your god now?
I imagine many languages do the same, but I lack the will to test it.
Anyway, of course, it would be more correct if it was considered whitespace... And I bet anything parsed in Haskell or Perl6 does such.