Is a single Cargo.lock for the whole workspace OK? #64
Description
If transitive dependencies of benchmark crates get changed when we add new benchmarks, should we have to invalidate past results? Can we "firewall" the benchmark crates' dependencies from each other while still having them able to use the local support crates?