Kirill Rakhman

I prefer option 3

You have a small typo in the title. Apart from that I obviously support this proposal.

I disagree with "not using objects as a namespacing mechanism". Sometimes there are functions that are only relevant in certain situations, for example operations on common collection classes. Making them...

Personally, I use a different style: ``` kotlin class C( val a: String, val b: String ) : SuperType { val d: String = "" } ``` This has the...

The formatter can be improved if it is decided that this style looks better.

Small addition for constructor annotations: ``` kotlin class Foo @Inject constructor( val prop: String ) { } ```

I wouldn't put the parantheses of the constructor on separate lines. 2016-06-14 20:55 GMT+02:00 Ruckus T-Boom [email protected]: > @kevinmost https://github.com/kevinmost I tried cleaning up your > suggestion a bit: >...

Use cases for `forEach`: - Nullable receiver: `list?.forEach {}` - Receiver is a return value that shouldn't be bound to a variable: `list.filter {}.forEach {}`

I would like to discuss the positioning of the companion object. In many cases it contains constants and constants are usually placed at the top of a class in Java....

Valid question. I guess not.