-
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 VecMap
#109280
Remove VecMap
#109280
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 6639538 with merge d1fbeb4125f24c53c41b7080d5e7b63753eb29bb... |
In general for small lengths the VecMap may be a win, since it avoids hashing and keeps items densely populated. This is especially true for small integer-like keys where iteration and comparison is likely to be very fast. But I suppose we can look at what perf comes back with at least to see whether any current benchmarks are negatively (or positively) affected. I suspect that for most compiler usage even if we wanted this we'd want it to be a hybrid between VecMap and FxIndexMap depending on length. |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Cool, thanks for the context. Yeah, I was just putting this up to see what would happen. If there is a perf hit, I wonder then, conversely, if there may be some benefit in backing |
Finished benchmarking commit (d1fbeb4125f24c53c41b7080d5e7b63753eb29bb): comparison URL. Overall result: no relevant changes - no action neededBenchmarking 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 Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
shrug, i still prefer to remove VecMap because it's only used for opaques, and it isn't hot enough to justify its special behavior r? compiler |
@bors r+ |
perf was neutral |
…-Simulacrum Remove `VecMap` Not sure what the use of this data structure is over just using `FxIndexMap` or a `Vec`. r? `@ghost`
…-Simulacrum Remove `VecMap` Not sure what the use of this data structure is over just using `FxIndexMap` or a `Vec`. r? ``@ghost``
Rollup of 11 pull requests Successful merges: - rust-lang#100311 (Fix handling of trailing bare CR in str::lines) - rust-lang#108997 (Change text -> rust highlighting in sanitizer.md) - rust-lang#109179 (move Option::as_slice to intrinsic) - rust-lang#109187 (Render source page layout with Askama) - rust-lang#109280 (Remove `VecMap`) - rust-lang#109295 (refactor `fn bootstrap::builder::Builder::compiler_for` logic) - rust-lang#109312 (rustdoc: Cleanup parent module tracking for doc links) - rust-lang#109317 (Update links for custom discriminants.) - rust-lang#109405 (RPITITs are `DefKind::Opaque` with new lowering strategy) - rust-lang#109414 (Do not consider synthesized RPITITs on missing items checks) - rust-lang#109435 (Detect uninhabited types early in const eval) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Not sure what the use of this data structure is over just using
FxIndexMap
or aVec
.r? @ghost