Darien Maillet Valentine
Darien Maillet Valentine
I read "directly" as specifying that h (indirectly contained) is not considered.
Ah, got it — “directly contained” only describes the declaration relative to the block, not the block relative to the “root” statement list.
Record field and slots name overlap occurs for these as well: - [[Capability]] - [[ECMAScriptCode]] - [[Environment]] - [[Module]] - [[Promise]] - [[Realm]] - [[Strict]] To me it seems especially...
Found a test in [test262](https://github.com/tc39/test262/pull/2613) related to this. The link in that PR goes to a Twitter thread where an implementor expressed uncertainty about the conformance requirements. The test appears...
Title update is to focus this issue on the Number case only, making it align with the work in the related PR, and a [new issue](https://github.com/tc39/ecma262/issues/2860) captures the BigInt part.
It allows caching results (of e.g. parsers of other languages) in association with the template literal parse node. Template tag functions can perform work related to the literal segments just...
> That is, it is an optimization. It can be, but it's affording an _identity_ associated with the parse node and this enables more than just performance optimizations. It is...
@dSalieri It sounds like you’ve got the idea. The final expression in the example devsnek gave is the part of the source text with its “identity” exposed to ES code...
> How do we get different results with the same template literals but different parse nodes? I’m not 100% sure what “the same template literals” means here, but since you’re...
> How do we get different results with the same template literals but different parse nodes? You wouldn't if "result" here means the template string array itself. The template string...