Axel Hecht

I think we're talking about one lightyear, 1 lightyear, but 1.0 lightyears. I added the `[one]` case to make room for something that actually has a multi-valued `[one]` or more...

Right now, no built-in functions are specified, including `NUMBER`. The specification process we're in right now is about exactly answering the questions you raised, and to decide what's a bug...

Let me turn the question around a bit, and talk about localizing your interface. How are localizers going to know what string to put in for those entries? And which...

I think that, high-level, zero-copy parsing isn't a design goal for fluent. I think that some implementations might benefit from it, but it does come with down-sides. I'm not so...

Wondering if that's always a single syntax node that can have just two whities, but we'll figure that out once we get there.

Yeah, this is a bug in the js (and probably python) impls. Also a bug here for not having exhaustive tests on that behavior. We had an earlier version of...

> But I believe that this feature can have a more subtle impact on Fluent ecosystem by nurturing the culture of thinking about the social contract. Instead of a culture...

General comments: We commonly read the grammars eagerly, so if a production is `Text | Foo`, you'll never get to `Foo`. I think we would say "Paramater has a Variable",...

I think there's value in `variant-key` being strict. This is mostly about the readability of the message. At the point where we have variants, that already goes down a fair...

TBH, I don't like the proposal. I didn't get to actually read it before just now, sorry. What I don't like in particular is introducing identifier and it's constraints in...