Skip to content

editorial: add a value liveness note #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

editorial: add a value liveness note #135

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions spec.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,11 @@ <h1>Agents</h1>
</tr>
</table>
</emu-table>

<emu-note>
<p>The value field [[AsyncContextValue]] in the list [[AsyncContextMapping]] of an Agent Record is only intended to be accessed via an [[AsyncContextKey]] field. The list is not iterable through AsyncContext APIs.</p>
<p>The above definition implies that, if a value in the [[AsyncContextKey]] field in an Async Context Mapping Record is not live, then its corresponding value of [[AsyncContextValue]] is not necessarily live either.</p>
Copy link
Member

@andreubotella andreubotella Sep 9, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the semantics here could be better expressed in two steps:

  • A live [[AsyncContextMapping]] does not necessarily keep its [[AsyncContextKey]]s alive
  • For a live [[AsyncContextMapping]], if an [[AsyncContextKey]] is not live, its corresponding [[AsyncContextValue]] is not necessarily kept alive.

</emu-note>
</emu-clause>

<emu-clause id="sec-weakref-processing-model">
Expand Down