Skip to content

Commit

Permalink
fixup: Insert "and async functions" into note re execution contexts
Browse files Browse the repository at this point in the history
  • Loading branch information
jmdyck committed Aug 17, 2023
1 parent 6c57ab0 commit e19db45
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion spec.html
Original file line number Diff line number Diff line change
Expand Up @@ -11746,7 +11746,7 @@ <h1>Execution Contexts</h1>
<h1>Execution Context Stack</h1>
<p>An agent's <dfn id="execution-context-stack" variants="execution context stacks">execution context stack</dfn> is used to organize some or all of the agent's execution contexts. The running execution context is always the top element of this stack.</p>
<p>Adding and removing always happens at the “top” of the execution context stack. When an execution context is added, it becomes the topmost (i.e., the running execution context), and when it is later removed, the execution context “below” it becomes topmost again.</p>
<emu-note>In the absense of generators, every execution context that is pushed onto the stack is new, and when it's removed from the stack it can be discarded. With generators, some execution contexts outlive their time on the stack, exist for a while outside the stack, and then later are pushed onto the stack again.</emu-note>
<emu-note>In the absence of generators and async functions, every execution context that is pushed onto the stack is new, and when it's removed from the stack it can be discarded. With generators and async functions, some execution contexts outlive their time on the stack, exist for a while outside the stack, and then later are pushed onto the stack again.</emu-note>
</emu-clause>

<emu-clause id="sec-getactivescriptormodule" type="abstract operation">
Expand Down

0 comments on commit e19db45

Please sign in to comment.