Well said, @arnetheduck. Honestly, for the true master, you could do some pluggable system that allowed macro/compile-time proc-driven identifier transformation with the current rules as a simple activation maybe as a pragma on `import`. Then people could override that current "compromise" batch of ident rules with something even more idiosyncratic (e.g., that handled ALL_CAPS or maybe CAPPREFIX_Foo identifiers differently, as needed/wanted). You might need to declare a convention inside defining modules, too, though, if you depart from the default.
Anyway, instead of quashing admittedly often time-waste-y arguments about (just some dimensions) of style with a totally unique set of ident rules (more than just "case insensitive" as @dom96 points out), give devs tools to manage disagreements.
