Ms2ger

As I recall, `ToDateTimeOptions` fills in a bunch of defaults that weren't appropriate to create the new Temporal patterns. The new approach was to read only the actually-provided options into...

> > Checking the downstream specs, nobody references `SetRealmGlobalObject`, `CreateRealm`, or `SetDefaultGlobalBindings`. > > It's worth noting that https://tc39.es/proposal-shadowrealm/#sec-shadowrealm will need an update. This is now done as part of...

More to the point, the AOs that shadow realms was using before got removed in this PR

Proposal: 1. Clarify the documentation 2. Use `phase: resolution` for `test/language/import/import-assertions/json-invalid.js` since we couldn't figure a use case to distinguish between your steps 2 and 3 3. Rewrite `test/language/module-code/source-phase-import/import-source-binding-name.js` as...

Unless they're in the `.any.js` default set, probably not

That sounds like the clearest solution, yeah

I don't have particularly strong opinions on the exact way to spec this, except that explicit is better than implicit and having the hook visible in the place where you...

The rest of the step is omitted in fig. 1: > 3. Otherwise, > 1. [Create a host function](https://wasm-dsl.github.io/spectec/js-api/#create-a-host-function) from v and functype, and let funcaddr be the result. >...

I don't recall off the top of my head

Thanks for the comment. ["react"](https://webidl.spec.whatwg.org/#dfn-perform-steps-once-promise-is-settled) does not deal with abstract closures (explicitly); WebIDL seems to only use abstract closures in two cases, and only when used as an argument to...