Addison Phillips

Why do you assume that the `.match` has no declarational effect? The opposite is certainly true (declarations affect the selector). I see no reason why the shorthand shouldn't work. Heck,...

@eemeli noted: > According to our current language, selector and placeholder expressions do not modify their operand beyond themselves. I can't find where we do that? The closest I can...

> The .match isn't a declaration, and so nothing happening in its selector expressions affects the resolution of variables in placeholders. I don't buy that argument. The text you quote...

@eemeli asked: > you would have an expectation of a formatting call with { x: 42 } as input to output 'x is 42.00', yes? Yes. Looking at that message,...

(as chair) Discussion of number selection using the same function as the formatter is a WG consensus and is documented in [Selection on Numerical Values](https://github.com/unicode-org/message-format-wg/blob/main/exploration/number-selection.md) in exploration. Discussion of this...

> I would like to push back hard on this... I consider it critical that function implementations not be able to modify anything in the context, and really to not...

@gibson042 Ironically, I think you and I are in violent agreement. The problem here is that our mental model of what the "formatting context" is differs. I think it is...

> According to the [LDML45 spec](https://unicode.org/reports/tr35/tr35-messageFormat.html#function-resolution), the only such value revealed to function implementations is the current locale. In the JS [Intl.MessageFormat proposal spec](https://tc39.es/proposal-intl-messageformat/#sec-resolvefunction), the localeMatcher and the expression source...

See my [comment](https://github.com/unicode-org/message-format-wg/pull/911#discussion_r1842758207) on #911.

with pr on timezone