PERF: use copy=False in constructor in unstack (CoW) #57458
Closed
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.
xref #57431
I think we are sure that the
valuesfromself.get_new_values(..), which we pass here to the DataFrame constructor, are always new values owned by us (not shared by any other object), and so we can safely setcopy=Falsein that case.Mimicking the
time_unstackbenchmark: