Implement JSON string escape in pure-awk (several orders of magnitude faster) #48
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.
I've got a very pathological branch of a certain repository where this makes a parallelized (four concurrent invocations) generation change from ~3 minutes down to ~13 seconds.
I did not implement
\b
or\f
because I don't think the chances of them occurring naturally in a text document (especially aDockerfile
) in 2022+ are very high. 😅(Also, this isn't required to be pure JSON, but rather "
jq
compatible" as it's used asjq
syntax so we have a little bit more wiggle room asjq
is more forgiving than a pure strict parser)