-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustdoc: Rename Type::ResolvedPath
to Type::Path
and don't re-export it
#91197
Conversation
I'm afraid that the new name is too generic: we already have |
It's the same name as |
It's different, not less generic. That was the main point. Well, maybe I'm the only who thinks that. What do you think @rust-lang/rustdoc ? |
@camelid @GuillaumeGomez can you please use Zulip threads instead of pings for low-impact things like this? I get a lot of pings and this isn't a user-facing change. |
Anyway, I think this isn't worth worrying about until #91195 is merged. |
This will allow re-exporting only certain enum variants.
I would like to rename it to `Type::Path`, but then it can't be re-exported since the name would conflict with the `Path` struct. Usually enum variants are referred to using their qualified names in Rust (and parts of rustdoc already do that with `clean::Type`), so this is also more consistent with the language.
c155fa7
to
9a09e07
Compare
It's merged now ;) |
I don't think it's a bad idea given that it's only a variant and directly contains a |
I don't have a strong opinion either. Well, I guess usage will tell. Unless you have something to do in this PR, r=me,jyn514. |
@bors r=GuillaumeGomez,jyn514 |
📌 Commit 9a09e07a55306ee4096d110af3c3395a3505dd9f has been approved by |
At last! The new name is shorter, simpler, and consistent with `hir::Ty`.
9a09e07
to
79c718f
Compare
Updated references to ResolvedPath. @bors r=GuillaumeGomez,jyn514 |
📌 Commit 79c718f has been approved by |
…askrgr Rollup of 7 pull requests Successful merges: - rust-lang#90611 (Fix another ICE in rustdoc scrape_examples) - rust-lang#91197 (rustdoc: Rename `Type::ResolvedPath` to `Type::Path` and don't re-export it) - rust-lang#91223 (Fix headings indent) - rust-lang#91240 (Saner formatting for UTF8_CHAR_WIDTH table) - rust-lang#91248 (Bump compiler-builtins to 0.1.53) - rust-lang#91252 (Fix bug where submodules wouldn't be updated when running x.py from a subdirectory) - rust-lang#91259 (Remove `--display-doctest-warnings`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
The new name is shorter, simpler, and consistent with
hir::Ty
. It can't bere-exported since the name would conflict with the
clean::Path
struct. Butusually enum variants are referred to using their qualified names in Rust anyway
(and parts of rustdoc already do that with
clean::Type
), so this is also moreconsistent with the language.
r? @GuillaumeGomez
cc @jyn514