IC mangling: Change mangling rules
1. Use 'x' for each parameter, which is not an inline class, every possible clash is handled by signature rather than name. This change makes more API changes binary-compatible. So, the changes are in line with the vision of inline classes are value classes, like primitives. 2. Take return type into account when mangling a function if the return type is inline class. Otherwise, boxing bridge will not be generated, which leads to CCE at runtime.
This commit is contained in:
+6
@@ -0,0 +1,6 @@
|
||||
// !LANGUAGE: +InlineClasses
|
||||
|
||||
inline class IC(val i: Int)
|
||||
|
||||
fun foo(i: Int, ic: IC) {}
|
||||
fun foo(i: Int?, ic: IC) {}
|
||||
Reference in New Issue
Block a user