## Motivation Intra-workspace dependencies can go out of sync if only referencing crates.io, where changing one crate locally and testing the whole library will result in errors stemming from two different versions of the same trait etc. This is hard to keep track of and makes development more difficult than it needs to be. ## Solution Afaik it's common practice to specify both a version and a path as per [the cargo docs]. This is what tokio does with its subcrates too. : https://github.com/rust-lang/cargo/blob/master/src/doc/src/reference/specifying-dependencies.md#multiple-locations.
|Type||Name||Latest commit message||Commit time|
|Failed to load latest commit information.|