gh-131196: Add C implementation of UUID stringification #140666
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.
This PR follows up on #140663 by, well, following up on my musing about whether there should be an optimized C implementation of UUID stringification.
I tried to tighten the C implementation as much as possible, e.g. by directly writing into an
1BYTE_KINDPyUnicode object (as e.g.pystrhex.cdoes, which I couldn't use here because of the unique separator situation UUIDs have). I'd appreciate extra eyes on it, though!The speedup seems pleasant for a fairly small patch – on my machine, some 4.5x: