I was looking at the rust api naming guidelines, and noticed this sentance:
UpperCamelCase, acronyms and contractions of compound words count as one word: use
UUID suggestion seems incorrect. In almost every other context I've seen, it's written as
UUID (with the remaining being
uuid for snake_case types and fields). In particular, in the Java Runtime library (which does use CamelCase convention for class names, similar to rust), the type is
java.util.UUID. Additionally, it is cased as UUID in [RFC 4122], the title of ISO 9834-8, and other relevant standards that define the format and documents describing it (https://en.wikipedia.org/wiki/Universally_unique_identifier).
Further, the spelling
Uuid reads differently from
UUID, at least to me. At an immediate glance,
UUID reads as a Univerally Unique Identifier, and
Uuid reads as some other form of Unique Identifier (without actually thinking about the name).
I'm wondering if anyone else is confused in the same way, and, if so, should the naming guidelines explicitly except this acronym from the rule, given the relative frequency of the former casing (and the fact the official casing seems to point to UUID).