fix issue 10772 std.regex.splitter generates spurious empty elements #1790
Conversation
This file contains 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
| //bugzilla 10772 | ||
| auto s3 = "test"; | ||
| assert(splitter(s3, regex("")).equal(["t", "e", "s", "t"])); | ||
| assert(splitter(s3, regex("x?")).equal(["t", "e", "s", "t"])); |
There was a problem hiding this comment.
Will this still create an empty token if there are two consecutive (non-empty) matches?
assert(splitter("texxt", regex("x?")).equal(["t", "e", "", "t"]));
There was a problem hiding this comment.
What about "xtestx"? "xxtestxx"?
There was a problem hiding this comment.
This pull does something strange ;). Perl does something curious.
If you know what rules it follows exactly it would be nice. I can't wrap my head around them.
|
Closing this due to controversy |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue 10772