Update values on uninitialized fields on module records
codehag opened this issue · 0 comments
codehag commented
in #161 @syg noted that for the new cycleRoot field, 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.