Issue 6024: Minimize number of render objects preallocated for the sprite component #6025
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
JCash
commented
Sep 2, 2021
| // Although we generally like to preallocate it, we cannot since we | ||
| // 1) don't want to preallocate max_sprite number of render objects and | ||
| // 2) We cannot keep the render object in a (small) fixed array and then reallocate it, since we pass the pointer to the render engine | ||
| if (sprite_world->m_RenderObjectsInUse == sprite_world->m_RenderObjects.Capacity()) |
There was a problem hiding this comment.
We just let it grow dynamically, so that we allocate a minimum amount of objects.
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.
No description provided.