Add sub signatures performance note to perldelta#24548
Open
bbrtj wants to merge 2 commits into
Open
Conversation
leonerd
reviewed
Jul 8, 2026
Contributor
|
Also while you're there, all of the entries should be their own |
edb6454 to
b87ab20
Compare
Leont
approved these changes
Jul 8, 2026
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
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.
This adds a note to perldelta about signatures having less runtime overhead due to internal changes made to support named parameters (or so I heard).
This was discussed on IRC, and I checked that there is indeed a performance difference. Here is the benchmark code:
It consistently shows
rawcase being ~25% faster thansignatureson 5.42, and ~5% faster on compiled blead. While this is not the best way to benchmark, that much of a difference should be enough to determine that indeed signatures are now more efficient. Note thatrawonly serves as a base for comparison here, so that we see efficiency difference between two variants of argument unpacking, without the need to take overall perl interpreter efficiency into account.Example results: