Tina L

It seems to be working as expected on main (and I believe in the 6.2 branch too since we haven't touched this after branching) ```swift let first = Calendar(identifier: .iso8601).firstWeekday...

I don't think we can ever change this without breaking existing clients. There are other API that requires this ordering, such as `Calendar.weekdaySymbols`, so the ordering is basically ABI stable...

`DateComponents` has a `Calendar` variable, and the convention is to refer calendar related information to the calendar. Given that this information is available in `Calendar`, adding this similar property on...

It is available everywhere. Is it this `@available(macOS 10.10, iOS 8.0, watchOS 2.0, tvOS 9.0, *)` that gave you this impression, or are you having issues accessing it from other...

The comment is very likely incorrect and needs to be updated. Is that your concern, or do you actually want a way to get back an empty string?

That's fair. Though as you probably know there's an easy way around this, which is to specify a `date:` alongside the `time: .omitted`

https://github.com/swiftlang/swift-foundation/blob/22d54679a83a66e2318d14c06f16c1d4c1df0ba2/Sources/FoundationInternationalization/Formatting/Date/DateFormatStyle.swift#L226 Looks like `.numeric` is the default

I don't think we'd want to fix it by changing the default argument from `nil` to `.numeric`. Their current behaviours are different: (I'm using en_GB so it's day/month/year) ```swift let...

@swift-ci please test