IcuLocaleData.NameIndexToNumericData is not linker friendly

[vargaz]

NameIndexToNumericData is a 15k byte array which cannot be linked out even through much of the information inside it is not needed if not all entries in IcuLocaleDataParts are used by the app. It would be better to have 1 array for each entry in IcuLocaleDataParts.

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @tannergooding, @sbomer
See info in area-owners.md if you want to be subscribed.

Issue Details

---

NameIndexToNumericData is a 15k byte array which cannot be linked out even through much of the information inside it is not needed if not all entries in IcuLocaleDataParts are used by the app. It would be better to have 1 array for every entry in IcuLocaleDataParts.

Author:	vargaz
Assignees:	-
Labels:	linkable-framework, untriaged
Milestone:	-

Tagging subscribers to this area: @tarekgh, @safern, @krwq
See info in area-owners.md if you want to be subscribed.

Issue Details

---

NameIndexToNumericData is a 15k byte array which cannot be linked out even through much of the information inside it is not needed if not all entries in IcuLocaleDataParts are used by the app. It would be better to have 1 array for each entry in IcuLocaleDataParts.

Author:	vargaz
Assignees:	-
Labels:	area-System.Globalization, linkable-framework, size-reduction, untriaged
Milestone:	-

[tarekgh]

@marek-safar @vargaz we need to decide for such issues if it is nice to have or it has to be fixed in 6.0. To know the priority and plan for that. Or you expecting your team will take care with that?

[marek-safar]

This was discussed in #45643 (comment)

@tarekgh teams working on size goals will take care of this when it fits into their priorities list.