Simple VRAM Allocator #60
Merged
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.
Replicate the logic of the previous allocator, but in safe code using a struct.
Right now the alloc functions return a unique chunk object with the start point and the length. This would almost certainly look more complex in a more robust allocator, since the allocator would likely want to keep track of the allocated chunks for itself, or have the chunks store references to other chunks. Happy to make this look any way that makes sense, this is all uncharted territory to me but has been a lot of fun to hack on.