A little consistency issue, here how classes shoul...
# kotlin-websitee
Eric Ou
08/08/2022, 3:52 AMA little consistency issue, here how classes should be named is described as "start with an uppercase letter and use camel case"
https://kotlinlang.org/docs/coding-conventions.html#interface-implementation-layout
Whereas here, a few paragraphs above, it is called "Use upper camel case with an uppercase first letter (also known as Pascal case)"
https://kotlinlang.org/docs/coding-conventions.html#source-file-names
v
Vampire
08/08/2022, 7:31 AMWhere is the inconsistency. What you quoted is the same just with different words, so it is consistent
e
Eric Ou
08/08/2022, 7:32 AMI would say calling it A and describing A is very much different, the thing it says is the same, but not the way it's said
v
Vampire
08/08/2022, 7:43 AMWell, it is inconsistent in concrete words, but not inconsistent in meaning. Latter would be a problem. :-)
e
Eric Ou
08/08/2022, 7:44 AMNot sure about that, I would say it's a bit of
A<B> vs B where B: A<B> situation.
v
Vampire
08/08/2022, 7:45 AMIsn't that just a formula for exactly what I said?
e
Eric Ou
08/08/2022, 7:46 AMWell not really, A<B> can't be passed to something that only takes B, if upper camel case has more info than just camel case with the first letter being capital, that would make it inexact! 😄
v
Vampire
08/08/2022, 7:54 AMBut it is the same. Upper camel case means camel case with the first letter upper cased.
Vampire
08/08/2022, 7:55 AMI don't see where you read more info in either
3 Views