Tony Parker
Tony Parker
The behavior was introduced in an attempt to avoid something like this: Time: 12:59:59.9999 Format: 3 digits of ms, rounding nearest Result: 12:59:59.000 Now, we could say that it should...
How much does this actually address the overall problem reported in #76555?
I don't want to aggressively cherry pick this back without any evidence that it resolves the named bug. We're already doing it on main, though.
Ok, thanks
https://github.com/swiftlang/swift-installer-scripts/pull/312 https://github.com/apple/swift-corelibs-foundation/pull/4990 https://github.com/apple/swift-foundation/pull/731 https://github.com/apple/swift-foundation-icu/pull/31 @swift-ci please test Windows platform
https://github.com/swiftlang/swift-installer-scripts/pull/312 https://github.com/apple/swift-corelibs-foundation/pull/4990 https://github.com/apple/swift-foundation/pull/731 https://github.com/apple/swift-foundation-icu/pull/31 @swift-ci please test Windows platform
`URL` is part of `FoundationEssentials`, so that could be the only requirement there.
FoundationEssentials is present on all non-Darwin platforms as part of the Swift toolchain. On Darwin it's still just Foundation.
`import FoundationEssentials` is available in Swift 6.0 or later. See [here](https://github.com/swiftlang/swift-foundation?tab=readme-ov-file#swift-foundation) for more information on how these are all layered.
If we run a proposal through swift-evolution and it includes extensions to Foundation API, and the Foundation workgroup doesn't object for some reason, then we can consider it accepted.