src: use validate_ascii_with_errors for buffer.isAscii #61122
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.
Tracking: #61041
Don't expect
buffer.isAsciicommon-case to be ASCII, as that's exposed as a public API for checks.The error version has better performance on non-ascii as it returns early, which could easily be e.g. >10x.
Refs: #46271 (comment),
But somehow the
_errorsversion is also faster on ASCII, which was supposed to be a common case forvalidate_ascii?I'm not sure what's up, might be a simdutf bug? cc @lemire
On another note: v8 is also likely using
validate_asciiincorrectlybuffer.isAsciiperf:main:
PR