diskern-core depends on dashmap and never mentions it:
$ grep -rn "dashmap\|DashMap" crates app --include=*.rs
$
It is declared in the root [workspace.dependencies] and taken in
crates/diskern-core/Cargo.toml, so it is compiled into every build of
the engine — it shows up in the build log right beside the crates the
engine actually uses:
Checking petgraph v0.8.3
Checking dashmap v6.2.1
Checking getrandom v0.4.3
Presumably left over from an earlier plan for the parallel walk, which
ended up with jwalk collecting into a Vec and rayon for the hashing.
The fix is to drop the line from crates/diskern-core/Cargo.toml and the
entry from the workspace table, then confirm
cargo test -p diskern-core -p diskern-cli still passes. An unused
dependency is build time and audit surface for nothing — the audit
ignore-list in .cargo/audit.toml is already long enough with the ones
Tauri forces on us.
crates/diskern-core/Cargo.toml:24 · Cargo.toml:31
diskern-coredepends ondashmapand never mentions it:$ grep -rn "dashmap\|DashMap" crates app --include=*.rs $It is declared in the root
[workspace.dependencies]and taken incrates/diskern-core/Cargo.toml, so it is compiled into every build ofthe engine — it shows up in the build log right beside the crates the
engine actually uses:
Presumably left over from an earlier plan for the parallel walk, which
ended up with
jwalkcollecting into aVecandrayonfor the hashing.The fix is to drop the line from
crates/diskern-core/Cargo.tomland theentry from the workspace table, then confirm
cargo test -p diskern-core -p diskern-clistill passes. An unuseddependency is build time and audit surface for nothing — the audit
ignore-list in
.cargo/audit.tomlis already long enough with the onesTauri forces on us.
crates/diskern-core/Cargo.toml:24·Cargo.toml:31