-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Update cargo #90490
Update cargo #90490
Conversation
|
@bors r+ p=1 |
📌 Commit 6404dba has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (dca3f1b): comparison url. Summary: This change led to moderate relevant regressions 😿 in compiler performance.
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 |
Visiting for weekly performance triage Only I don't think its worth investing effort trying to figure out the root cause of this limited regression. (I will note that regression #31157 was itself put in to catch a performance regression with respect to time and RAM, but that regression was more like 1,882% in time and 10x in space.) @rustbot label: +perf-regression-triaged |
3 commits in 6c1bc24b8b49d4bc965f67d7037906dc199c72b7..94ca096afbf25f670e76e07dca754fcfe27134be
2021-10-24 17:51:41 +0000 to 2021-10-29 14:45:06 +0000
HashMap::from
rather than collectingVec
of tuples (Chore: preferHashMap::from
rather than collectingVec
of tuples cargo#10018)