Francesco Vasco

I fully agree with @altavir. I perceive the `!!` as a cast, it looks strange on a type. ~~~ var s: String? println(s!!) // println(s as String) ~~~ Honestly, I...

In the section [VM ABI and Java compatibility](https://github.com/Kotlin/KEEP/blob/11d003e5c625ed9fc042954aeb9fd831cefed2aa/proposals/context-receivers.md#jvm-abi-and-java-compatibility), the Kotlin code: ```kotlin context(C1, C2) fun R.f(p1: P1, p2: P2) ``` should be equal the Java code ```java public static final...

@edrd-f please consider that `context()` is already valid Kotlin syntax.

@nunocastromartins I consider more readable the parameters declaration, like the context's one, before the return type. However, we need/prefer some kind of brackets? Should a comma separated list enough? ```...

@altavir sorry, I miss the point. Can you explain better?

`inline sealed class` is union type for Kotlin In such case we should consider also `inline object Baz : Base()`

@LouisCAD https://github.com/Kotlin/kotlinx.coroutines/issues/330

Hi @RaisedByTheInternet how you define `UInt.MAX_VALUE`? The following statement is invalid const val MAX_VALUE: UInt = UInt(0xFFFF_FFFF) C has the same issue. Inline classes miss of encapsulation. Have you some...

I wish bring to your attention another common use case, I hope that considering a bit more complex problem can help us to understand the simpler one. I want to...

Please sorry for my trivial question, but I missed something important. If a `value class` is an immutable data type, why is it important to mark a property like a...