Tina L
Tina L
@swift-ci please test
I'd expect this to be fixed with https://github.com/apple/swift-foundation/commit/d0d8a1830503ea590e09789d43304934575dc983?
Yes we have a radar for implementing localized contain: 104656368. We can create an issue as well if we think that helps keeping things on track.
Currently `.withFractionalSeconds` requires the string to contain fractional seconds, and decoding would fail if it doesn't. Just as a general survey -- Do all strings contain fractional seconds, or some...
We can't change the behavior of `Date.ISO8601FormatStyle` or `ISO8601DateFormatter` so that `withFractionalSeconds` parses both strings **with** and **without** the fractional seconds if the current behavior requires strict matching. We can...
My point was that we can't simply "fix this bug" by changing the behavior. It's important to maintain compatibility for clients who are relying on the current strict behavior. So...
[`Duration.FormatStyle`](https://github.com/apple/swift-foundation/blob/main/Sources/FoundationInternationalization/Formatting/Duration%2BUnitsFormatStyle.swift) is available!
It's currently impossible to extend localization support to custom `Dimension`, unfortunately. Currently we rely exclusively on ICU to fetch the localization. I imagine we'd need to add a hook in...
Is this resolved by https://github.com/apple/swift-foundation/pull/262?
As far as I know `gmtime` doesn't seem to promise correctness before Gregorian calendar came into effect. That would also explain why we're only seeing test failures on `distantPast`, which...