Eemeli Aro

Would this example be perhaps easier to reason about? ``` let $appleCount = {$amount :number minimumFractionDigits=1} match {$appleCount :plural} when one {You have {$appleCount} apple} when * {You have {$appleCount}...

It seems to me that we're mixing here concerns from multiple different layers of the implementation. To get at something like a root of this, could we see if we...

I'm okay with not hoisting, as long as referring to variables defined earlier is considered valid: ``` let $bar = {$count :number ...} let $foo = {$bar :number ...} ```

Here's one real-world-ish example of a possible use case: ``` # $selected (number) - A Unix timestamp in milliseconds let $time = {$selected :datetime timeStyle=short hourCycle=h23} let $date = {$selected...

> Questions about example you provided: > > > datetime accepts numeric input and a basket of options matching the JS Intl.DateTimeFormat constructor. Its resolved value is a Date object...

> So `:datetime` returns what? To answer this fully, it's perhaps easiest for me to use the [JS Intl.MessageFormat proposal](https://github.com/tc39/proposal-intl-messageformat) and [its polyfill](https://github.com/messageformat/messageformat/tree/master/packages/mf2-messageformat) to provide specific examples. As we've discussed...

I'm having a hard time imagining how exactly a sensible hard restriction on function names could be worded, given that we're rather unlikely to have a single standard library shared...

What if `$foo` here was defined by a local variable, such that its type was available? That could well make sense if the same value was being used both for...

There was a bug in updating the offset during composition for empty mapping values with trailing comments. Thank you for reporting this! Fixed version released as v2.1.2.

Bother; you're right. I'd found first a minimal example that appeared to trigger the same error, and solved against that only.