[FIR] Make sure the primary constructor is first in class CFG
The primary constructor of a class needs to be the first subgraph of the class control-flow graph. Based on the Kotlin specification, class initialization order goes first primary constructor, in-place declarations (properties and init blocks), and then secondary constructors. If the class doesn't have a primary constructor, then it is just skipped in the order. Unfortunately, the class control-flow graph had in-place declarations first and then all constructors. Instead, we should treat the primary constructor as the first in-place declaration, and then continue with the existing processing as secondary constructors. This will guarantee that super constructor calls have the correct property initialization information. ^KT-65093 Fixed
This commit is contained in:
Vendored
+6
-6
@@ -33,15 +33,15 @@ digraph functionCallBound_kt {
|
||||
7 [label="Enter class Sub" style="filled" fillcolor=red];
|
||||
subgraph cluster_4 {
|
||||
color=blue
|
||||
8 [label="Enter property" style="filled" fillcolor=red];
|
||||
9 [label="Access variable R|<local>/data|"];
|
||||
10 [label="Exit property" style="filled" fillcolor=red];
|
||||
8 [label="Enter function <init>" style="filled" fillcolor=red];
|
||||
9 [label="Delegated constructor call: super<R|Base|>()" style="filled" fillcolor=yellow];
|
||||
10 [label="Exit function <init>" style="filled" fillcolor=red];
|
||||
}
|
||||
subgraph cluster_5 {
|
||||
color=blue
|
||||
11 [label="Enter function <init>" style="filled" fillcolor=red];
|
||||
12 [label="Delegated constructor call: super<R|Base|>()" style="filled" fillcolor=yellow];
|
||||
13 [label="Exit function <init>" style="filled" fillcolor=red];
|
||||
11 [label="Enter property" style="filled" fillcolor=red];
|
||||
12 [label="Access variable R|<local>/data|"];
|
||||
13 [label="Exit property" style="filled" fillcolor=red];
|
||||
}
|
||||
14 [label="Exit class Sub" style="filled" fillcolor=red];
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user