Specifying template strings
allen at wirfs-brock.com
Thu Jul 10 08:52:40 PDT 2014
On Jul 10, 2014, at 7:31 AM, Axel Rauschmayer wrote:
>>> – Tagged templates are explained via EvaluateCall(tagRef, TemplateLiteral, tailCall). I think it would be easier to understand if it used GetTemplateCallSite.
>> Because a Tagged Template is a call. Would it be clearer if there was a note that highlighted the fact that the actual TemplateLiteral provides the argument list for the call?
> Yes. Naively, I’d expect the result of a TemplateLiteral to be a string. But I previously didn’t understand the difference between static semantics and runtime semantics. The indirection makes things more difficult to follow, but I assume it helps with writing the specification (given proxies, generators etc.).
Static semantics is about things about or which can be derived from just the source code, independent of the actual execution of the code
Runtime semantics is about what actually happens when the program executes and typically has dependency upon the runtime state of the program.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss