-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move icu::calendar::week to experimental #6157
Comments
This code is also used to determine the first day of the week, and the weekend. Only the |
Yeah. So maybe only move the "bad parts" to experimental. |
They can't be moved, they're all on the same type. Unless you want to remove the We can just make those methods private if you don't want them to be stable in 2.0 |
But I think we should hide the methods behind an experimental feature. Or private, but probably experimental. |
I don't think this justifies adding an experimental feature. They are not experimental, they work, and they have been stable for multiple releases. If we say they are footguns, we should remove them until a client asks for them. |
I think having an experimental feature should be seen as having a very low cost. It isn't something that should factor very highly into our calculus
And CLDR plans to deprecate this functionality in favor of a different algorithm
They aren't footguns; they are soon but not yet deprecated
I would approve a PR removing them. But then we should probably also remove the field from the data struct. |
Ideally we would have experimental code in
CLDR is talking about deprecation because they are footguns:
|
Given https://unicode-org.atlassian.net/browse/CLDR-18275, it is unclear that this code in its current state is what we will need. I think we should mark it as experimental.
The text was updated successfully, but these errors were encountered: