pyos
a9be27e330
Quick quiz:
Q: In a CFG, what does `a -> b -> c -> d` mean?
A: `a`, then `b`, then `c`, then `d`.
Q: In a CFG, what does `a -> b -> d; a -> c -> d` mean?
A: `a`, then `b` or `c`, then `d`.
Q: So how do you encode "a, then (b, then c) or (c, then b), then d`?
A: You can't.
Problem is, you need to, because that's what `a; run2({ b }, { c }); d`
does when `run2` has a contract that it calls both its lambda arguments
in-place: `shuffle(listOf(block1, block2)).forEach { it() }` is a
perfectly valid implementation for it, as little sense as that makes.
So that's what union nodes solve. When a node implements
`UnionNodeMarker`, its inputs are interpreted as "all visited in some
order" instead of the normal "one of the inputs is visited".
Currently this is used for data flow. It *should* also be used for
control flow, but it isn't. But it should be. But that's not so easy.
BTW, `try` exit is NOT a union node; although lambdas in one branch can
be completed according to types' of lambdas in another, data does not
flow between the branches anyway (since we don't know how much of the
`try` executed before jumping into `catch`, and `catch`es are mutually
exclusive) so a `try` expression is more like `when` than a function
call with called-in-place-exactly-once arguments. The fact that
`exitTryExpression` used `processUnionOfArguments` in a weird way
should've hinted at that, but now we know for certain.
49 lines
1.4 KiB
Plaintext
Vendored
49 lines
1.4 KiB
Plaintext
Vendored
digraph simple_kt {
|
|
graph [nodesep=3]
|
|
node [shape=box penwidth=2]
|
|
edge [penwidth=2]
|
|
|
|
subgraph cluster_0 {
|
|
color=red
|
|
0 [label="Enter function foo" style="filled" fillcolor=red];
|
|
subgraph cluster_1 {
|
|
color=blue
|
|
1 [label="Enter block"];
|
|
2 [label="Exit block"];
|
|
}
|
|
3 [label="Exit function foo" style="filled" fillcolor=red];
|
|
}
|
|
0 -> {1};
|
|
1 -> {2};
|
|
2 -> {3};
|
|
|
|
subgraph cluster_2 {
|
|
color=red
|
|
4 [label="Enter function test" style="filled" fillcolor=red];
|
|
subgraph cluster_3 {
|
|
color=blue
|
|
5 [label="Enter block"];
|
|
6 [label="Const: Int(1)"];
|
|
7 [label="Variable declaration: lval x: R|kotlin/Int|"];
|
|
8 [label="Access variable R|<local>/x|"];
|
|
9 [label="Const: Int(1)"];
|
|
10 [label="Function call: R|<local>/x|.R|kotlin/Int.plus|(...)" style="filled" fillcolor=yellow];
|
|
11 [label="Variable declaration: lval y: R|kotlin/Int|"];
|
|
12 [label="Function call: R|/foo|()" style="filled" fillcolor=yellow];
|
|
13 [label="Exit block"];
|
|
}
|
|
14 [label="Exit function test" style="filled" fillcolor=red];
|
|
}
|
|
4 -> {5};
|
|
5 -> {6};
|
|
6 -> {7};
|
|
7 -> {8};
|
|
8 -> {9};
|
|
9 -> {10};
|
|
10 -> {11};
|
|
11 -> {12};
|
|
12 -> {13};
|
|
13 -> {14};
|
|
|
|
}
|