Split non-ASCII Uri normalization out of ParseRemaining and avoid temporary allocations #122038
+228
−276
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.
Review without whitespace changes
When we rebuild the
_stringfor inputs with non-ASCII chars, we do so in two places:PrivateParseMinimalrecreates the string up to the path (scheme, user info, host, port)ParseRemainingrecreates the path, query and fragmentParseRemainingis currently written along the lines ofThis makes it much harder to reason about because we're juggling two offsets into two different strings, while also changing one of them.
This PR splits the rebuilding logic into a separate helper we call first that normalizes the path/query/fragment.
Since all the transformations now happen in a single place, we can also easily avoid the ~5 temporary string allocations.
We're still allocating the host separately, but that can be improved later.
Benchmark