Scott Schafer

Part of workspace inheritance is the ability for a member to inherit the `edition` from its workspace. #10587 was opened to discuss if setting the `edition` in `[workspace.package]` should imply...

@hi-rustin If you don't mind I would like to claim this. I want to add it to the RFC as something to do before we try to stabilize.

I'm currently working on the [RFC for workspace inheritance](https://github.com/rust-lang/rfcs/pull/2906) and would like to add this issue to the [tracking issue](https://github.com/rust-lang/cargo/issues/8415) as something to do before trying to stabilize it.

That's my bad for being confusing. I was just trying to say that I was just going to add it to my todo list before trying for stabilization of workspace...

Another thing to consider is having `workspace.edition = true` caused #10586 to some degree. By having things to inherit under `workspace.package.{key}` or `[workspace.package]`, it makes it harder to mix up...

With workspace inheritance being stabilized, and #10112 being brought up again (#10910 would close it). I was wondering if this was something to consider again before it would be a...

It looks like this happens because a fuzzy search for a `PathSoruce` returns all packages and `cargo_add` enables fuzzy searching in `get_latest_dependency`. The simple solution would be to turn off...

Yeah it would cause it to outright fail. I think throwing an error here is the best course of action as bypassing a source replace feels wrong as it wouldn't...

Yes, putting `[workspace]` in a manifest marks it as the [root package](https://doc.rust-lang.org/cargo/reference/workspaces.html#root-package). This makes it so it won't search for another workspace root as the package is the root.

`psuedo-outer-attribute namespacing` should not be considered unless it comes from a different crate. It could cause problems when someone is new to the codebase and wants to look up how...