CLDR-18217 Make CLDRFile Iterable interface include extra paths by default

[btangmu]

-Private boolean CLDRFile.DEFAULT_ITERATION_INCLUDES_EXTRAS determines whether to skip extras; either way they skip paths with null values

-Rename old iterator iteratorWithoutExtras

-Iterable and iterator are distinct, as in iterableWithoutExtras versus iteratorWithoutExtras

-Call iteratorWithoutExtras/iterableWithoutExtras directly where tests would otherwise fail with DEFAULT_ITERATION_INCLUDES_EXTRAS true

CLDR-18217

• This PR completes the ticket.

ALLOW_MANY_COMMITS=true

[btangmu]

I'm not sure whether this should go into v47 or wait for v48. Another option would be to make DEFAULT_ITERATION_INCLUDES_EXTRAS false for v47 (preserving current behavior), and change it to true for v48. There are risks either way. Changing a lot of paths to extra paths (without code-fallback values) has increased the risk that some unknown bugs exist due to skipping extra paths. Including extra paths in iteration could also introduce bugs. Either way, the bugs in question aren't covered yet by unit tests, and they could be tools that are run infrequently.

[macchiati]

Let's not change behavior from v46.1 this late in the game.

[btangmu]

Let's not change behavior from v46.1 this late in the game.

Understood. What do you think about making DEFAULT_ITERATION_INCLUDES_EXTRAS false, and merging it that way?

[macchiati]

Only if we verify that there are no differences in resolved values.

…

On Wed, Feb 12, 2025 at 12:03 PM Tom Bishop ***@***.***> wrote: Let's not change behavior from v46.1 this late in the game. Understood. What do you think about making DEFAULT_ITERATION_INCLUDES_EXTRAS false, and merging it that way? — Reply to this email directly, view it on GitHub <#4371 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJLEMEBUA4DHZ6RQVVBOQL2POSJZAVCNFSM6AAAAABXAK24RSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJUG4ZDMNRUGY> . You are receiving this because you commented.Message ID: ***@***.***>