-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Remove is_spotlight field from Trait
#80914
Conversation
d20dfd5
to
19d6700
Compare
7254d97
to
2ef594d
Compare
@camelid would you like to review? |
@jyn514 Thanks for giving me the opportunity to review! :) I'll give it a look, but it's probably still a good idea for you to take a look as well since I'm still learning the intricacies of rustdoc. |
(Marking as blocked on #80883.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this field being removed because it's only used in one place and we don't want to pile stuff onto clean::Trait
?
☔ The latest upstream changes (presumably #81240) made this pull request unmergeable. Please resolve the merge conflicts. |
…n514 Remove CACHE_KEY global We realized in rust-lang#80914 that the cache handling (through a global) needed to be updated to make it much easier to handle. r? `@jyn514`
2ef594d
to
e86f706
Compare
Rebased! Only the last commit is from this PR, the others still come from #80883. cc @CraftSpider @ollie27 |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. As far as I can tell this should behave the same, just with spotlight calculated at use instead of early. Only question is: How is spotlight_decl called, will this end up duplicating the spotlight lookup? Not too terrible if it does, but want to make sure I understand.
Trait
Trait
That's actually a pretty good point. It forces us to run this check every time a function returns a "spotlighted" item. That's not great. |
* Improve documentation * Add a test to ensure that spotlighted traits from dependencies are taken into account as expected
1593598
to
33aaead
Compare
I updated the description but I'll keep the mention to the other PR. ;) |
@bors: r=jyn514 |
📌 Commit 33aaead has been approved by |
⌛ Testing commit 33aaead with merge f46c0e49c6121d2ea31376c25c1ac1b7b91d0c91... |
💥 Test timed out |
@bors: retry |
☀️ Test successful - checks-actions |
I didn't make these renames in rust-lang#80965 because I didn't want the PR to conflict with rust-lang#80914.
…ht, r=GuillaumeGomez rustdoc: Rename internal uses of `spotlight` I didn't make these renames in rust-lang#80965 because I didn't want the PR to conflict with rust-lang#80914.
Small PR, only the last commit is relevant here. The rest is coming from #80883 because I need the
TyCtxt
stored insideCache
.The point is to make ItemKind looks as close as possible to the compiler type so that it makes the switch simpler (which is why I make all these "small" PRs).
r? @jyn514