Skip to content

Conversation

@MrAwesome
Copy link
Collaborator

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.

@MrAwesome MrAwesome changed the title Simple API for VRAM allocator, and simple implementation of it Simple VRAM Allocator Jul 8, 2020
Copy link
Owner

@overdrivenpotato overdrivenpotato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great aside from these two nits

@MrAwesome
Copy link
Collaborator Author

Alright! Should be good to go.

@overdrivenpotato overdrivenpotato merged commit 6b2c31e into overdrivenpotato:master Jul 9, 2020
@overdrivenpotato
Copy link
Owner

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants