Eemeli Aro
Eemeli Aro
@angryzor That looks pretty great! We should take a closer look at this once number range formatting is a bit more widely supported.
How did you envision that this would work? TypeScript does not provide a plugin support for custom types (microsoft/TypeScript#10939), so you're probably either asking for a process that would generate...
> Extractors do not provide reflection. You cannot take a `function f(Point(x, y)) {}` function object and reflect that the first argument takes a `Point`, just as you also cannot...
> Extractors are not the correct feature to build runtime types on. While you can use extractors for runtime assertions, their purpose is to augment destructuring. IMO, a better feature...
Consider making ResolveLocale return the normalized requested locale instead of the available locale
> However, `supportedLocalesOf()` echoes back entries from the `requestedLocales` list. To be specific, from the canonicalized list of requested locales. ```js Intl.NumberFormat.supportedLocalesOf('EN-us') → ['en-US'] ```
As noted above, support for Python < 3.6 has already been dropped.
Closing, as modern VS Code correctly detects the symlinked file as Python.
Excellent, thank you! I'll have to look at this in more detail a bit later. A few months ago I started to port the code to ES6; that work is...
I believe we've settled on not including comments, notes or metadata within the message syntax, at least in the 2.0 spec.
I've put together eemeli/message-resource-wg#19 as a place to continue this discussion.