@tbkka Thoughts?

I'm reluctant to add this to the default (non-locale-aware) initializer.

Two concerns:

1. I want to leave the default initializer here very plain with no options so we can drive performance for things like JSON parsing.
2. As Richard says, this is true "in English" but other languages handle things differently.

I would prefer a separate initializer such as `Double("10,204", locale: ....)` or `Double("10,204", options: ...)` that can handle this in varying ways depending on needs. There are likely other designs, of course; I don't think we yet have an established pattern for how to handle locale-sensitive issues in the standard library.

@stephentyrone Do you have a better idea?

Comment by Richard Aurbach (JIRA)

Actually, I agree with Tim Kientzie. I've been considering an extension of Double that does this. Should be quite simple to do. Actually, let me restate my original post:

There should be a standard way to convert user-entered numeric strings (of all relevant types) to handle common user input strings, such as numbers which contain group separators. And this should be done in a locale-aware way.

I'm fine with XXX(_:String, locale: Locale) where XXX is Int, Double, Float, etc. I just think that since converting user input is a common use of these initializers, that it would be a good addition to Standard Library to include them.

Locale-dependent formatting is something that we've fairly intentionally wanted to keep out of the standard library (and leave to higher-level libraries).

It's an important feature, but not all important features need to live in the standard library proper. Foundation already provides this functionality (and much more), FWIW: https://developer.apple.com/documentation/foundation/numberformatter