Force specialization on the type argument of _similar_for
#30331
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.
Looking into the
["misc", "iterators", "zip(1:1, 1:1, 1:1, 1:1)"]
regression reported in #30218 (comment), it looks like #28284 pushed theHasShape
method of_similar_for
beyond the inlining threshold for that case, causing the regression. Adding a@_meta_inline
would directly combat that, but forcing specialization on the type argument is less invasive and still restores performance:I hope @nanosoldier
runbenchmarks(ALL, vs = ":master")
agrees. In that case, I guess we want this on 1.1 as well.I vaguely remember having noticed this when working on #29238 but decided it was an orthogonal change to be done in a separate PR and then forgot about it...