Skip to content

Conversation

@yotamofek
Copy link
Contributor

@yotamofek yotamofek commented Nov 29, 2025

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. labels Nov 29, 2025
@yotamofek
Copy link
Contributor Author

yotamofek commented Nov 29, 2025

@lolbinarycat Felt like doing something semi-mechanical that doesn't require too much concentration, so thought I'd tackle the issue you opened.

But TBH, after pulling out the common code into an IndexItem constructor, I'm not sure it makes much sense and/or is worth it.
What do you think?

@rust-log-analyzer

This comment has been minimized.

@yotamofek yotamofek force-pushed the pr/rustdoc/IndexItem-new branch 2 times, most recently from 32d0484 to 6cedf2c Compare November 29, 2025 17:13
@rust-log-analyzer

This comment has been minimized.

@lolbinarycat
Copy link
Contributor

It was working on #149460 that inspired this issue, and I agree that perhaps a substruct would be a better approach.

@yotamofek yotamofek force-pushed the pr/rustdoc/IndexItem-new branch from 6cedf2c to acd4d7e Compare December 12, 2025 22:32
@yotamofek
Copy link
Contributor Author

What do you think about how it looks now? @lolbinarycat
(still need to find a better name for the "sub struct")

@yotamofek
Copy link
Contributor Author

the amount of times I typed "sub stract" instead of "sub struct"....... 😤

@lolbinarycat
Copy link
Contributor

IndexItemInfo maybe? then the field could just be named info

@yotamofek yotamofek force-pushed the pr/rustdoc/IndexItem-new branch from a39f59d to 86a2e85 Compare December 15, 2025 20:26
@yotamofek yotamofek marked this pull request as ready for review December 15, 2025 20:27
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Dec 15, 2025
@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Dec 15, 2025
@rustbot
Copy link
Collaborator

rustbot commented Dec 15, 2025

r? @GuillaumeGomez

rustbot has assigned @GuillaumeGomez.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@yotamofek
Copy link
Contributor Author

Well, done, not sure it's an improvement, but let's see what others think.

@GuillaumeGomez
Copy link
Member

Changes look good to me. So if it's ok with lolbinarycat and notriddle, you can r=us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants