Relocate memory-allocation specific files to their own path #2339
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
mazunki
force-pushed
the
feat-allocator-paths
branch
from
ddc004a to
352458c
Compare
mazunki
force-pushed
the
feat-allocator-paths
branch
from
352458c to
57fb728
Compare
Contributor
Author
Done, tests are still 🌈 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As I will be adding more allocators going forward, it's useful to have a dedicated location for different allocators. This creates the
mem/andmem/alloc/include paths for this purpose.This also matches more closely to the namespace
os::memwe were already using.I suppose putting those files in
util/was initially a temporary solution which just stuck around.