Dmitry Petrov
b5f37d18b2
When two functions with matching JVM signatures in the same package were inlined sequentially, inliner could take a wrong method body from the cache due to MethodId clash. This manifested with inline classes, but also was possible with some legal Kotlin overloads with matching erasure. Use internal name of the corresponding implementation owner class instead of FQN of the containing declaration. Such MethodIds can't match accidentally, because corresponding JVM method signatures would clash.
12 lines
367 B
Plaintext
Vendored
12 lines
367 B
Plaintext
Vendored
warning: ATTENTION!
|
|
This build uses unsafe internal compiler arguments:
|
|
|
|
-XXLanguage:+InlineClasses
|
|
|
|
This mode is not recommended for production use,
|
|
as no stability/compatibility guarantees are given on
|
|
compiler or generated code. Use it at your own risk!
|
|
|
|
warning: following manually enabled features will force generation of pre-release binaries: InlineClasses
|
|
OK
|