Alexander Udalov
f0282bcfdf
The change is a bit complicated because the name mapping logic is refactored so that we would compute the needed suffix first (either module name, or multifile part class name), and then shove it into the mangled name between the original function name and "$default", if the function in question is the default arguments adapter. The main motivation for this change was to fix KT-41809, but as a side effect, private functions with default arguments in multifile parts now also contain the file name, just like normal private functions. #KT-41809 Fixed
14 lines
1.0 KiB
Plaintext
Vendored
14 lines
1.0 KiB
Plaintext
Vendored
@kotlin.Metadata
|
|
public final class test/A {
|
|
// source: 'internalNameMangling.kt'
|
|
public method <init>(): void
|
|
public method <init>(p0: int): void
|
|
public synthetic method <init>(p0: int, p1: int, p2: kotlin.jvm.internal.DefaultConstructorMarker): void
|
|
public synthetic static method internalFunction$test_module$default(p0: test.A, p1: java.lang.String, p2: int, p3: java.lang.Object): void
|
|
public final method internalFunction$test_module(@org.jetbrains.annotations.NotNull p0: java.lang.String): void
|
|
public synthetic static method internalJvmNameFunction$default(p0: test.A, p1: java.lang.String, p2: int, p3: java.lang.Object): void
|
|
public final @kotlin.jvm.JvmName method internalJvmNameFunction(@org.jetbrains.annotations.NotNull p0: java.lang.String): void
|
|
public synthetic static method publicFunction$default(p0: test.A, p1: java.lang.String, p2: int, p3: java.lang.Object): void
|
|
public final method publicFunction(@org.jetbrains.annotations.NotNull p0: java.lang.String): void
|
|
}
|