This message was deleted.

this is an endless argument, and I’m not going to begin another round of it. suffice to say, Google’s Android style guide also has the same convention, and I’m not going to either contradict them or try to convince them to change their style guide

This is why I would just avoid making any statements about it and I woild let developers do it how they want. Note that Kotlin/Native is opening Kotlin to lot's of new environments and platforms (Python, R etc) and they will not be happy if developers will be forced to change their naming habits.

following that logic we might as well give up on the style guide altogether. and the community has clearly stated that one is needed.

It is not a point. Conventions are needed but not just for making conventions. They are needed when there is some purpose behind them. I feel that this rule is not improving anything. Stating that something is constant says nearly nothing - most properties in Kotlin are read-only.

@marcinmoskala Gson() is not a constant

@Andreas Sinz It is clear, but isn't it a top-level property holding data? I think that this is not clear

@marcinmoskala At the beginning it starts with

Names of constants

.

properties that hold data

probably can be confusing

OK

the Android style guide contains a fairly elaborate definition of what is and isn’t a constant. we might just copy that

After consideration I think that your argumentation is good and this is why I deleted my suggestion. Although some clarification might be useful.

I’ve clarified the text based on the wording in the Android style guide