-
Notifications
You must be signed in to change notification settings - Fork 13.9k
rustc_serialize: don't allocate Strings as key for BTreeMap, when str is enough
#91626
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
|
(rust-highfive has picked a reviewer for you, use r? to override) |
Strings as key for BTreeMap, when str is enought
|
@bors r+ |
|
📌 Commit 1b27b69 has been approved by |
rustc_serialize: don't allocate `String`s as key for `BTreeMap`, when `str` is enought
rustc_serialize: don't allocate `String`s as key for `BTreeMap`, when `str` is enought
|
This should affect perf (at least, this is was idea), so @bors rollup=never |
|
@klensy: 🔑 Insufficient privileges: not in try users |
|
@bors rollup=never |
Strings as key for BTreeMap, when str is enoughtStrings as key for BTreeMap, when str is enough
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (6d6d089): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
No description provided.