You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means that this library will be responsible for vending the necessary parts of ICU to support Localization of currency formats, as well as currency symbols.
This is not a trivial feature
The text was updated successfully, but these errors were encountered:
After several years of thinking about this - I think it's fine to rely on Foundation to avoid duplicating a lot of work for supporting currency formatting.
A lot of the differences between Swift versions is really the difference between ICU versions, which makes sense as it updates to stay current with changing Locales.
I think if this was to be kept as a feature request, what it would end up being is a wrapper aroundNumberFormatter to highly specialize it for currency and not a general purpose number formatter.
Honestly, most projects should be using Currency Style - my understanding is that the format styles are orders of magnitude faster than the old style Foundation formatters.
Honestly, most projects should be using Currency Style - my understanding is that the format styles are orders of magnitude faster than the old style Foundation formatters.
That's a good point. I honestly forgot about those APIs 😅
Goal
To remove reliance on
Foundation
, which leaves us vulnerable to bugs introduced between Swift versions and more control over a nicer API for currency formatting instead ofFoundation.NumberFormatter
.Implications
This means that this library will be responsible for vending the necessary parts of ICU to support Localization of currency formats, as well as currency symbols.
This is not a trivial feature
The text was updated successfully, but these errors were encountered: