feat: add OOM safe constructors - #372
Open
khanhtranngoccva wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I am currently attempting to implement a OOM friendly polyfill for standard popular Rust data structures.
The current API of DashMap is not sufficient to allow implementing OOM-safe abstractions on top of it. Currently, the HashSet lacks facilities to retrieve the hasher to implement TryClone semantics, and for both types, there are no constructors that can fallibly deal with initial allocation, making try_reserve much less useful in practice.
This PR is a minimal attempt to allow construction of DashMap and DashSet fallibly. It also exposes the ability of DashSet to cast and convert to and from DashMap to implement polyfills if any needed low level API is somehow missing.