Fix #78308: IntlPartsIterator key is wrong for KEY_LEFT/KEY_RIGHT #4446
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.
We must not increase the iterator's index after it has been properly
determined. A clean solution would be to increment the index in the
internal
*_move_forward()
methods instead ofIntlIterator::next()
,but since the
*_move_forward()
methods are currently also called bythe internal
*_rewind()
methods, and don't have a flag to determinethe (intent of the) caller, we apply a hack for now.
We also fix the erroneous expectations of an existing test case.