perlapi: Consolidate the sv_eq and svstr_eq entries #23824
Merged
Conversation
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
These functions do the same thing, differing in details. Consolidation makes perlapi more compact, and makes it easier for the reader to see the similarities and differences between the functions. Note that the cryptic sentence "It correctly handles the UTF8 flag" in the sv_streq entry has been removed. It turns out that meant that the code looks at the UTF8ness of each SV, except when 'use bytes' is in effect.
tonycoz
approved these changes
Oct 8, 2025
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.
These functions do the same thing, differing in details. Consolidation makes perlapi more compact, and makes it easier for the reader to see the similarities and differences between the functions.
Note that the cryptic sentence "It correctly handles the UTF8 flag" in the sv_streq entry has been removed. It turns out that meant that the code looks at the UTF8ness of each SV, except when 'use bytes' is in effect.