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.
23 lines
455 B
TOML
23 lines
455 B
TOML
[package]
|
|
name = "nac3artiq"
|
|
version = "0.1.0"
|
|
authors = ["M-Labs"]
|
|
edition = "2021"
|
|
|
|
[lib]
|
|
name = "nac3artiq"
|
|
crate-type = ["cdylib"]
|
|
|
|
[dependencies]
|
|
indexmap = "2.7"
|
|
itertools = "0.14"
|
|
pyo3 = { version = "0.21", features = ["extension-module", "gil-refs"] }
|
|
parking_lot = "0.12"
|
|
tempfile = "3.16"
|
|
nac3core = { path = "../nac3core" }
|
|
nac3ld = { path = "../nac3ld" }
|
|
|
|
[features]
|
|
init-llvm-profile = []
|
|
no-escape-analysis = ["nac3core/no-escape-analysis"]
|