-
Notifications
You must be signed in to change notification settings - Fork 13k
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
stop using FnCtxt
outside of hir typeck
#99015
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit f40f608c067f0cbb1ffd0d2d284da302119ac96a with merge 3c6f387d68a4200acd27290e70f49c68ac4ddd62... |
@rust-timer build 3c6f387d68a4200acd27290e70f49c68ac4ddd62 |
Queued 3c6f387d68a4200acd27290e70f49c68ac4ddd62 with parent c461f7a, future comparison URL. |
the last commit is relevant for perf again @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 6fb4b0449f4b3038cf978017f088a3e9e6532814 with merge 5f8f3a7067fe8e90fa3b126f966aa67f7c180e60... |
☀️ Try build successful - checks-actions |
@rust-timer build 5f8f3a7067fe8e90fa3b126f966aa67f7c180e60 |
Finished benchmarking commit (3c6f387d68a4200acd27290e70f49c68ac4ddd62): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Footnotes |
@rust-timer build 5f8f3a7067fe8e90fa3b126f966aa67f7c180e60 |
Queued 5f8f3a7067fe8e90fa3b126f966aa67f7c180e60 with parent eba361a, future comparison URL. |
Finished benchmarking commit (5f8f3a7067fe8e90fa3b126f966aa67f7c180e60): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Footnotes |
This comment was marked as outdated.
This comment was marked as outdated.
@rustbot ready |
☔ The latest upstream changes (presumably #99278) made this pull request unmergeable. Please resolve the merge conflicts. |
this was previously used for opaque types but became unnecessary after rust-lang#89024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@bors r=compiler-errors |
☀️ Test successful - checks-actions |
Finished benchmarking commit (23e21bd): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Signed-off-by: Yuki Okushi <[email protected]>
Signed-off-by: Yuki Okushi <[email protected]>
the requirements between hir typeck™, and not hir typeck™ are different enough to warrant a full split. with this PR
FnCtxt
is now only used for hir typeck (and for one clippy lint which seems to be emulating hir typeck).Once this PR has landed I intend to move
FnCtxt
into a new crate. This should also allow some further general improvements here.r? rust-lang/types