Alejandro Serrano

> This seems overly restrictive. IMO it's obvious that `@all:[A B]` would apply `A` to all targets `A` can be applied to, and `B` to all targets `B` can be...

@jesperancinha yes, this is currently being implemented, and we expect these new features to appear in 2.2

@MartinHaeusler @jesperancinha this feature is to be fully announce in 2.2.0, but there's a experimental version available in 2.1.20 under the `-Xannotation-default-target=param-property` flag.

The KEEP has been merged, and the feature should be fully announced by 2.2.0, as experimental. This PR will remain open for some time after that release to gather additional...

PS: This also updates Kotlin to 2.1.0-Beta2, since 2.0.21 was giving a very weird compiler error.

It seems that this breaks in Native. The error is now [reported in YouTrack](https://youtrack.jetbrains.com/issue/KT-72281/Failed-to-wait-for-cache-to-be-built-with-Kotlin-Native)

Thanks for the fast feedback! We're indeed monitoring the upcoming changes in Valhalla, but there are a few comments. The goal of this KEEP is to expose a Kotlin API...

Let me reiterate why I think that, regardless of the upcoming value class support in the JVM, exposing a "non-inlined" version of Kotlin's `@JvmInline value class` is useful. People want...

On this discussion, I would like to distinguish two different positions which I feel are getting mixed up: 1. Kotlin should stop doing inline as soon as possible, and switch...

Just to clarify: this KEEP changes *nothing* about the view Kotlin has of an inline value class. All of the “boxed variants” of callables are only available to Java, the...