Manish Goregaokar
Manish Goregaokar
yes, I am asking to see the code. I think this discussion is not possible without being able to determine if that code really should be doing that and if...
Also if it's a zero thing we can still say something of the form that it's approximate but zero means zero
Okay, I think we have two paths: - We should declare that zero means zero, everything else is approximate, because that gives the most utility to users whilst leaving things...
I think that could work, though I think in that case we still would want to be able to signal the difference between "empty" and "hint zero".
This is referring to the [experimental DateTimeFormatter API](https://unicode-org.github.io/icu4x/docs/icu_datetime/struct.DateTimeFormatter.html#method.resolve_components). A bunch of this will probably change under skeletons anyway. @zbraniecki to approve.
Yes, you can ask questions here or on GitHub Discussions. We also have [email protected]
Proposal: 1. Continue printing a warning in datagen when a request language falls back to `und`@ro in an unexpected way 2. Do NOT retain the base language if the language...
oh, I wasn't aware there was an MSRV.
Sounds good!