Shane F. Carr

I think the spec should just normatively require support for combined number and currency/unit input types. Each implementation can do that in their own way. When an upgraded type is...

Previously, week-of-year was handled internally in the datetime formatter. However, in the semantic skeleton world and with flexible input types, I would rather move the week number calculations out into...

Yeah fair point. There are two designs already: the old one (where WeekCalculator is loaded in the formatter) and the one suggested in https://github.com/unicode-org/icu4x/issues/5643#issuecomment-2408973458 (which is a major shift, encoding...

As far as the semantic skeleton API goes: My thinking for a while has been that it should just be a new field set. `Year + Week`, a new Calendar...

- @sffc I see this as a calendrical calculation - @robertbastian DayOfYearInfo has all the info you need - @Manishearth I think it is a display concern - @robertbastian -...

2.0 work is to load the data correctly.

OK so regarding the week numbering things. Wikipedia has a good article on this subject: https://en.wikipedia.org/wiki/Week#Other_week_numbering_systems There are multiple possible schemes. ISO-8601 is the most common, but there are others....

Yeah, I'm not sure why I was briefly convinced thismorning that week numbering was a display concern. It absolutely is not! Exclamation point there. It is a data model concern....

Here's how I envision the use case. You are a public health agency and wish to use a week calendar for your web site. You create a `Date`. That object...

Without defining a new calendar, we could just model it as a `pub struct Week` living alongside `pub struct Date`. It could be a type defining a specific week in...