Currently, dev-util/rustfmt pulls in dev-lang/rust and causes long compile times, while it should work as well with dev-lang/rust-bin. Hence virtual/rust seems to be a better choice. I created some rust code and applied rustfmt successful without dev-lang/rust installed.
Is there any reason to object against this change?
It makes some amount of sense. On the other hand, on rustup setups, a rust toolchain now optionally includes rustfmt as a separate component, so I would prefer in the direction of pulling that in as part of the rust/rust-bin ebuilds.
The rustup way to handle this is that every tool match a toolchain version, at least if you install them with rustup component. This decision should propagate to all the non-cargo rust components (clippy, rls, analysis, etc).
This has been fixed, since the cargo eclass now pulls in virtual/rust.
