fix(deps): update rust crate dashmap to 5.5.3 - autoclosed #246
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.5.0
->5.5.3
Release Notes
xacrimon/dashmap (dashmap)
v5.5.2
Compare Source
This release merely reverts #259 since it introduced data race violations. We'll look into this more in the coming time and try to investigate why and how to gain back the additional 0.5%-ish lost performance. Additionally, v5.5.1 has been yanked.
Thanks to @Turbo87 and the crates.io team for reporting this issue.
v5.5.1
Compare Source
This release includes a couple of internal changes such as committing
Cargo.lock
as well as minor optimizations to lookup performance.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.