[pʲɵs]

JVM: do not assume presence of default method handle arguments

4

I believe Jetpack Compose is not generating them, and that's what's causing KT-58243. Adding them is obviously an ABI-breaking change.

FE: don't lose annotations on Java primitive arrays

2

^KT-48861 Fixed

JVM: do not erase Array<T> if T is reified

2

inline fun Any?.foo() = this is Array should be equivalent to inline fun Any?.foo2() = this is T inline fun Any?.foo() = foo2() but right now it isn't. (Does this...

...in builder inference mode, anyway. The new field serves the same purpose as ResolvedAtom.subResolvedAtoms in FE1.0: resolved named references no longer contain candidates, so type variable info needs to be...

If the super class is in a file that has already been lowered, the base method has an extra continuation parameter which breaks things. Also, SAM wrappers around functional objects...

I.e. if T is already bounded by Any, deserialize T&Any as simply T (instead of producing either an error type or an NPE, the latter happening when the T&Any is...

This avoids a crash due to circular class references through annotation arguments.

cc @udalov I'm doing my best here but the core problem is that reified type parameters are severely under-defined. [The main piece of design documentation here](https://github.com/JetBrains/kotlin/blob/master/spec-docs/reified-type-parameters.md) basically defines "runtime-available types"...