-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Fix hack that remaps env constness. #99521
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
Conversation
WARNING: might have perf implications. Are there any more problems with having a constness in the `ParamEnv` now? :)
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 8464396 with merge c95b5ba98e182bab01bc996efe8503c2e0e5be8f... |
☀️ Try build successful - checks-actions |
Queued c95b5ba98e182bab01bc996efe8503c2e0e5be8f with parent be9cfb3, future comparison URL. |
Finished benchmarking commit (c95b5ba98e182bab01bc996efe8503c2e0e5be8f): 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
This might just be noise because the benchmarks related to the trait system that I expect could regress didn't (diesel and other benchmarks). Instead all regressions are on the doc mode. @oli-obk can you please double check my analysis and add the triaged label if you agree? Thanks. Edit: I would also want to know if storing constness in the param env is okay. |
a small rustdoc regression |
This is probably due to rustdoc moving everything through the trait solver multiple times.
|
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (22d25f2): 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. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
WARNING: might have perf implications.
Are there any more problems with having a constness in the
ParamEnv
now? :)r? @oli-obk