I comment on this below, but just try doing a path = "" dep to a 3rd party workspaced project inside a workspaced project and see what happens. I'd have to dig

I comment on this below, but just try doing a path = "" dep to a 3rd party workspaced project inside a workspaced project and see what happens. I'd have to dig through old chat logs to find the specific explosions, but cargo did not like this. (It's possible it's been fixed in recent Cargo versions, but that's not available to me.) But in the end, cargo is a tool primarily designed for building crates that depend on crates in crates.io. Even workspaces themselves are a bit of a half-baked afterthought. But cargo really should have started by looking at Maven for inspiration -- a) a moderated repository and b) Maven has much more expressive support for version restrictions etc. Instead crates.io feels like it's going the way of the world npm. Anyways, sorry if this sounds like "get off my lawn", I'm grouchy today.