Jake Wharton

What's the use case?

`TypeName.STAR` will give you the `*`. Then just parameterize a `TypeName` which represents `Class` using it.

No. And without a compelling case for it we have no plans to. Sorry.

I think the counterpoint is when you're writing it as statements in a body so I'm not sure omitting is a great default either. In Kotlin it actually feels like...

Tough to pull this off without breaking like 100% of users though. Might be time to rework the whole "code" part of the API.

I made the second example a non-empty block and things got weirder: ```kotlin public override val descriptor: SerialDescriptor = buildClassSerialDescriptor("RowVerticalAlignment") { element("direction") } ``` Here's the code: ```kotlin addProperty(PropertySpec.builder("descriptor", SerialDescriptor)...

```kotlin public override fun equals(other: Any?): Boolean = other is AccessibilityDescription && other.`value` == `value` ``` Beginning to think expression body support was a mistake because it seems to be...

That seems like a missing IDE warning. Java has http://errorprone.info/bugpattern/FloatingPointLiteralPrecision. On Tue, Sep 3, 2019 at 11:21 PM Zac Sweers wrote: > I like the idea of this, but the...

Seems like https://youtrack.jetbrains.com/issue/KT-20837 On Tue, Sep 3, 2019 at 11:27 PM Zac Sweers wrote: > huh, TIL > > — > You are receiving this because you commented. > Reply...

Thanks, I hate it! ```kotlin public fun ComoseGenerationTestRow(scoped: @Composable RowScope.() -> Unit, unscoped: @Composable () -> Unit): Unit { ``` I might be angry enough to rage fix this (it...