@stahlbrandt @anderseknert what a stereotypical set of responses from the go creators, oh my god

It's like they are intentionally obtusely pretending to not understand the rationale behind the question

And think disallowing var true = false is a waste of resources because one could simply define var True = false, which isn't a good reason at all

Predeclared identifiers have a standard meaning, shadowing them to something else is bad, their commentary is wack

"but the rule is so simple"