A modern programming language that makes developers happier.

kotlinlang

I wonder about coding conventions - the class layout:
```The contents of a class should go in the following order:

Property declarations and initializer blocks

Secondary constructors

Method declarations

Companion object```
What would be the reasoning of placing companion object at the end?  (just personal style, or there is some actual argument behind it?)

I guess it's because it's least touched / remains constant mostly.

I was wondering the same thing about `companion object` but it didn’t cross my mind to ask here :smile: and it’s good idea
I used to put it first, above everything

<@UK0BH8CJZ> makes sense. in Java for example statics are defined first, on the very top of the class tho :confused: :thinking_face:

Must be a Kotlin-thing as syntax could influence on the position. I put `const val`s at the very top too.