Norman Walsh
Norman Walsh
In discussion at the [Prague f2f](https://qt4cg.org/meeting/minutes/2024/06-04.html), the consensus seemed to support an `$options` map on the expectation that the map would be a literal, constant value in the overwhelming majorit...
I'm open to the idea, but it sounds to me like you're going to have to have wholly separate resolvers in each thread. I don't think the design would easily...
Consensus in Prague was that an extra serialization option to turn on the look-ahead behavior might be worth doing.
Also in Prague, we should go the standards route and represent `NaN` and the flavors of infinity with `null`.
Part of a nexus of issues related to variable arity dynamic functions. (See minutes of 4 June, 2024)
At [meeting 134](https://qt4cg.org/meeting/minutes/2025/09-16.html), the CG agreed to close this issue without further action.
Consensus of the folks present in Prague: provide a stack trace in errors, but not as a stand alone function.
That's interesting. It may just be that I imagined formal objects would always be numbered. I guess they don't have to be, but if there's more than one, what should...
That's an interesting one. I'm a little concerned about possible consequences where attribute values contain things that *should* be escaped. I'm a little surprised that the browser doesn't do the...
At [meeting 131](https://qt4cg.org/meeting/minutes/2025/07-29.html), the CG agreed to close this issue without further action.