Eemeli Aro
Eemeli Aro
> If it's unrepresentable in the data model, that means either that (1) (at least some) duplicate declaration errors have to be checked at parse time, or that (2) Message...
> Maybe I don't know enough about TypeScript, though, and there's a more abstract way to express this. The proposed TypeScript definition is using a JavaScript [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map), which retains insertion...
Out of interest in what "_not_ simple" would mean in practice, I wrote up the following function, which checks that an unordered map of declarations does not contain any reference...
Dropping, as pushing for these changes isn't worth the bother.
This won't make it into 48.
I think falling back to `h23` is the least worst option here.
The only real-world use of `24:00` as a time that I'm aware of is in Japan's [30-hour system](https://ja.wikipedia.org/wiki/30%E6%99%82%E9%96%93%E5%88%B6), where closing times past midnight until 6am may be indicated by times...
Brainstorming a bit, the string concatenation angle of this could be averted by defining a new local variable type that takes pattern values and can only be used in _option_...
If we do want to delegate the consideration of this to the resource space, then it would be very helpful if [eemeli/message-resource-wg](https://github.com/eemeli/message-resource-wg/) could be transferred under `unicode-org`.
Given that we've removed the promise of forward-compatibility, the reservation asked for here is made implicitly.