forked from M-Labs/nac3
David Mak
6265d53ad5
In the past, modules (and therefore its members) are not added or analyzed in order of appearance, as it is stored in a HashMap with the PythonId as its key. While this never posed an issue in the past, the refactoring performed in #535 assumed that the classes *are* ordered by appearance, causing the bug to manifest. Furthermore, this bug will only manifest iff a base class has a PythonId greater than the derived class, explaining why the bug only occurs on occasion. Fix this by using an IndexMap, which preserves the order of insertion while also performing deduplication. |
||
|---|---|---|
| .. | ||
| demo | ||
| src | ||
| Cargo.toml | ||