Clarify statement about pooling#11999
Open
taangle wants to merge 1 commit into
Open
Conversation
skyace65
added
enhancement
area:getting started
Calinou
approved these changes
May 17, 2026
Member
Calinou
left a comment
Calinou
left a comment
There was a problem hiding this comment.
Makes sense to me.
There can be a performance benefit to object pooling in GDScript, but GC pauses are not a problem in GDScript so it's less critical.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Small change for the note about pooling seen here
Right after the explanation of what pooling is, the current text says "When working with GDScript, you don't need to worry about this." To me this doesn't leave room for acknowledging any reason to use pooling other than avoiding freezes in GC languages.
You could argue that the current text is correct because it says "you don't need to", which leaves room for cases where the developer wants to use pooling. But if a game's performance is bottlenecked on instantiating and destroying lots of the same type of object, then pooling may actually become a need. Happy to have this rejected if pooling is truly useless in GDScript