Open rm-dr opened 9 months ago
It took me a little while to track down what you were referring to, so, for posterity:
I think we're not using it simply because it's a relatively new feature. It is possible that intra-workspace dependencies might cause some wrinkles that I would need to deal with in my Cranko release automation tool, but ... also maybe not?
Is there a reason we're not using
{ workspace = true }
in sub-crateCargo.toml
files? It would be nice to specify crate paths and versions in exactly one place, instead of listing all versions of all dependencies independently in each crate.