Build tuples in a single allocation - #3070
Merged
Merged
Conversation
Do not reallocate memory for the components field in B_tupleD___init__. Instead make the components field (tail of struct) a flexible array member. This halves the memory usage for constructing tuples.
mzagozen
force-pushed
the
tuple-single-allocation
branch
from
August 20, 2026 06:30
994799f to
6e8b6f1
Compare
mzagozen
enabled auto-merge
August 20, 2026 06:30
Contributor
|
LGTM :) I have been trying to think whether there is a potential issue about the box of boxed objects being of variable size. Should be fine as-is. It is conceivable we could put a box on the stack and perhaps that would be harder, but I don't think that is very appealing anyway. @nordlander you saw this, right? |
Contributor
|
Yup, this is ok with me. It might even have been my original intention!😉 |
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.
Do not re-allocate memory for the components field in B_tupleD___init__. Instead make the components field (tail of struct) a flexible array member. This halves the memory usage for constructing tuples.