Tom Hvitved 0ee5fe88d9 CIL: Account for multiple VariableUpdate::getSource()s in nullness analysis ...

For methods compiled without optimization (and possibly also with optimization),
it is possible for a variable update to have multiple possible assigned values.
For example, the non-optimized CIL for

```
return cond ? null : "not null"
```

is

```
0: nop
1: ldarg.0
2: ldfld cond
3: brtrue.s 6:
4: ldstr "not null"
5: br.s 7:
6: ldnull
7: stloc.0 L0 // stores either `null` or "not null"
8: br.s 9:
9: ldloc.0
10: ret
```

Consequently, an existential in `CallableReturns.qll` must be a `forex`.

2019-05-28 10:13:00 +02:00

..

consistency

C#: Autoformat QL files

2019-01-11 13:55:28 +01:00

dataflow

CIL: Account for multiple VariableUpdate::getSource()s in nullness analysis

2019-05-28 10:13:00 +02:00

pdbs

C#: Update expected outputs.

2019-03-19 15:11:19 +00:00

regressions

C#: Fix whitespaces

2018-12-12 13:13:13 +01:00