Explore potential CLDR locale data byte savings by omitting trailing undefined values #42315
Assignees
Labels
area: build & ci
Related the build and CI infrastructure of the project
area: common
Issues related to APIs in the @angular/common package
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Milestone
Comments
This was referenced Feb 11, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As noted by @petebacondarwin in #42230 (comment). Mostly for tracking
In the CLDR locale data we often output data as followed:
[a, b, undefined, undefined]. This is basically the same as[a, b]- as long as we don't care about the length of the array.We might be able to further improve this by trimming any trailing
undefinedvalues from the locale array.It's unclear whether this could land in a minor/patch, or whether we should wait for a major. If experiments show that we can do this optimization, then we could figure out where to land it. I assume a major is more suitable in case users rely on the locale data length (for unknown reasons?)
The text was updated successfully, but these errors were encountered: