Closed
Conversation
Owner
Author
|
I've opened a PR BurntSushi/bstr#223 that should improve the situation without resorting to Still, the |
Owner
Author
|
Closed in favour of #417. |
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
1 participant
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 increases performance of
lengthby up to 8x and roughly restores the performance of jq 2.7 (which does not have to account for non-UTF-8 strings). See also BurntSushi/bstr#221.At the same time, this also omits a cast to
isize, which could lead to wrong results forlengthwhen loading very large data, e.g. a byte string that contains more thanisizebytes.