e079fb665e
For subclasses of `AbstractMutableList<Int>` which are not inline classes, the special bridge `remove` had a parameter of type `Int` (mapped to JVM primitive int) before this fix. The hack in `MethodSignatureMapper` changed this type to `Int?`, yet the body of the special bridge still loaded it as non-nullable, which resulted in incorrect bytecode. It looks like a part of this hack in `BridgeLowering` was made only for inline classes which are subclasses of mutable collections. Supposedly it should be extended to non-inline classes, so that `remove` special bridge would have consistent IR by the time it reaches codegen. #KT-46516 Fixed
6 lines
125 B
Kotlin
Vendored
6 lines
125 B
Kotlin
Vendored
// WITH_RUNTIME
|
|
|
|
abstract class AMListD : AbstractMutableList<Double>()
|
|
|
|
abstract class AMListI : AbstractMutableList<Int>()
|