Open sffc opened 23 hours ago
For 2.0 Final I would like every function involving fieldsets to have docs pointing to the fieldset module. Plus every trait like AllAnyCalendarFormattingDataMarkers should explain what its common bounds mean i nrelation to fieldsets, and what to do when the trait isn't implemented.
(I'm in favor of all bullet points here. Replacing convert_and_format seems fine, we only have it because that was the initial behavior of the module and we wanted to keep it)
There were some questions about the name of IsAnyCalendarKind
Did you want to weigh in on what this trait should be called? I had recorded a comment that someone didn't like the name but didn't have an alternative. I'm personally still happy with the name.
No strong opinions, fine with the name. IsConcreteCalendar
perhaps.
No strong opinions, fine with the name.
IsConcreteCalendar
perhaps.
I'd kinda like to move it to icu_calendar
since it is in the same realm of functionality as IntoAnyCalendar
. Can you suggest an appropriate trait signature?
I'd say the same one?
One thing to note is that Calendar
already has this functionality, what this trait gets us is rather datetime-specific: "if you care about a calendar, is this the right calendar, or no?" I don't see that as particularly useful for calendar consumers.
For 2.0 Beta:
NeoSkeletonLength
should beLength
IsAnyCalendarKind
format_iso
function onDateTimeFormatter
, possibly replacingconvert_and_format
strict_format
should maybe beformat_same_calendar
FormattedNeoDateTime
should beFormattedDateTime
DateTimePatternFormatter
should have a single genericformat
functionDateTimePatternFormatter
and friends should useFSet
instead ofR
DateTimeNames::with_pattern
should betry_with_pattern
andwith_pattern_unchecked
(https://github.com/unicode-org/icu4x/issues/4336#issuecomment-1868376498)For 2.0 Final: