Split SpannedTypeVisitor into its own crate, rustc_ty_walk - #160362
Split SpannedTypeVisitor into its own crate, rustc_ty_walk#160362joshtriplett wants to merge 2 commits into
SpannedTypeVisitor into its own crate, rustc_ty_walk#160362Conversation
`rustc_privacy` pulls in all of `rustc_ty_utils`, but only wants `SpannedTypeVisitor` and `walk_types`. Move those to a small `rustc_ty_walk` crate. This allows `rustc_privacy` to start building much sooner.
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
|
r? @fee1-dead rustbot has assigned @fee1-dead. Use Why was this reviewer chosen?The reviewer was selected based on:
|
This comment has been minimized.
This comment has been minimized.
|
You need to bless bootstrap, see https://github.com/rust-lang/rust/blob/main/src/bootstrap/README.md#testing |
There was a problem hiding this comment.
Is there a way to just move these to be defined to rustc_privacy directly?
There was a problem hiding this comment.
@fee1-dead They're used by both rustc_ty_utils and rustc_privacy, so they need to be in a common crate available to both. I don't want to make rustc_ty_utils depend on rustc_privacy, and I don't think they logically fit in rustc_privacy.
There was a problem hiding this comment.
Logically it probably fits in rustc_middle - not that I want to move stuff there.
|
@rustbot ready |
|
I think we should consider splitting up crate A: Queries that need |
rustc_privacypulls in all ofrustc_ty_utils, but only wantsSpannedTypeVisitorandwalk_types. Move those to a smallrustc_ty_walkcrate.This allows
rustc_privacyto start building much sooner.