-
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 some function fields #80883
Remove some function fields #80883
Conversation
Let's check the perf results too while we're at it. @bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit 38100f17d2ad1a3c9f177abf49b0f1e50eb61c1e with merge 1977d4945b2c970bc1d8b2849d0eeb0d0cbb8e24... |
☀️ Try build successful - checks-actions |
Queued 1977d4945b2c970bc1d8b2849d0eeb0d0cbb8e24 with parent 080ee6f, future comparison URL. @rustbot label: +S-waiting-on-perf |
Finished benchmarking try commit (1977d4945b2c970bc1d8b2849d0eeb0d0cbb8e24): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
Interesting:
Much better than what I expected. |
@camelid would you like to review the change? |
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.
Here's a few comments.
I don't think I have enough knowledge of this code to be the reviewer, but I did leave a few comments. |
38100f1
to
e4d599e
Compare
c006ffb
to
b8e5ee6
Compare
☔ The latest upstream changes (presumably #81240) made this pull request unmergeable. Please resolve the merge conflicts. |
b8e5ee6
to
4c2c0b1
Compare
I made the PR back from the start based on the lastest developments. No more need for Confirming that the performance improvement is still there: @bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit 4c2c0b152785a5826fd45430d7f6e3f087271cd9 with merge bdc8ba6d71c33ac2e37bb4e7da6544dde3d300d3... |
01d333d
to
c92b161
Compare
Rebased. |
There is some good cleanup here but as I've tried to say the @bors r+ |
📌 Commit c92b161 has been approved by |
⌛ Testing commit c92b161 with merge 6dd633a726a1900af8a4c6a769809093b6cf3aa1... |
💥 Test timed out |
@bors retry |
☀️ Test successful - checks-actions |
…=jyn514 Remove is_spotlight field from `Trait` Small PR, only the last commit is relevant here. The rest is coming from rust-lang#80883 because I need the `TyCtxt` stored inside `Cache`. 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`
Based on rust-lang#80883 (comment). The `tcx` parameters do seem to be used though, so I only removed the `cache` parameters.
Same kind as #80845.
This PR removes the
all_types
andret_types
from theclean::Function
type.Another change that I had to do was implementing the
From
trait to be able to converthir::def::DefKind
intoclean::TypeKind
without requiringDocContext
(and so I updated theclean
method so that it's taken into account).The last two commits improve a bit the
get_real_types
function and theType::generics
method.r? @jyn514