Import third party collections and use internal Allocator API #631
Conversation
This file contains 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
udoprog
force-pushed
the
allocator-api
branch
15 times, most recently
from
70b2bb6 to
c1692a3
Compare
udoprog
force-pushed
the
allocator-api
branch
from
c1692a3 to
e0741e8
Compare
udoprog
force-pushed
the
allocator-api
branch
from
a7741f9 to
a197225
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a WIP moving collections over to an internal fallible allocator API.
This is the first step towards implementing memory sandboxing, since that requires allocator-level control.