PR: #26 (feat/01-scaffold-workspace)
Commit: cb1a5eb
File: Cargo.toml, [workspace] section, resolver = "2"
Problem: Rust edition 2024 (Rust 1.85) activates feature resolver v3 by default. Declaring resolver = "2" explicitly overrides that default and reverts to older resolver. alloy 0.8 with features = ["full"] has a large optional feature graph; resolver 2 vs 3 differs on feature unification for dev/build/test sets. Mismatch causes subtle feature-flag divergence as dep tree grows.
Impact: Feature unification in alloy and tokio sub-crates will not match edition-2024 expectations. Retro-diagnosis mid-dev requires re-auditing activated feature set.
Fix: Remove resolver key (edition 2024 implies resolver 3), or set resolver = "3" explicitly. If resolver 2 is intentional, add inline comment explaining why.
PR: #26 (feat/01-scaffold-workspace)
Commit: cb1a5eb
File: Cargo.toml,
[workspace]section,resolver = "2"Problem: Rust edition 2024 (Rust 1.85) activates feature resolver v3 by default. Declaring
resolver = "2"explicitly overrides that default and reverts to older resolver. alloy 0.8 withfeatures = ["full"]has a large optional feature graph; resolver 2 vs 3 differs on feature unification for dev/build/test sets. Mismatch causes subtle feature-flag divergence as dep tree grows.Impact: Feature unification in alloy and tokio sub-crates will not match edition-2024 expectations. Retro-diagnosis mid-dev requires re-auditing activated feature set.
Fix: Remove
resolverkey (edition 2024 implies resolver 3), or setresolver = "3"explicitly. If resolver 2 is intentional, add inline comment explaining why.