You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a reason we're not using { workspace = true } in sub-crate Cargo.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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: