This repository has been archived by the owner on Aug 29, 2021. It is now read-only.
Update values on uninitialized fields on module records #164
Comments
codehag
added a commit
to codehag/proposal-top-level-await
that referenced
this issue
Feb 3, 2021
codehag
added a commit
to codehag/proposal-top-level-await
that referenced
this issue
Feb 3, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
in #161 @syg noted that for the new
cycleRootfield, it should be specified as~empty~rather than*undefined*, as undefined is not a valid value there, rather the field starts as uninitialized, and through execution is filled. @guybedford noted we have a few such fields.We should update the spec to better reflect the current convention in 262.
The text was updated successfully, but these errors were encountered: