Bradley Farias

@ljharb global, mmm no it would still have a home realm, but being safely passable between home/target realms without leaking the home realm. this would require: ```js protocol InterfaceName {...

I need to rephrase all of this with a more concrete example. ```js // safe realm const vm = require('vm'); const unsafeRealm = vm.createContext(); let lastId = 1; const ids...

@ljharb `.implement(target, iface)` can specifically see the target before assigning the `HasId.id` and hook up the prototype/primordials. However, this means `o1[HasId.id] === o2[HasId.id]` is not always true.

looking back on this, it would be a channel to get primordials that would not otherwise be accessible like grabbing them off `Object.create(null)`. However, if `.implement` does it based upon...

This is true, I have lots of docs on this from our node loader work, but would prefer if we could sync up and try and disseminate what the pieces...

https://github.com/package-community/discussions/issues/2 is relevant I would like to note my dislike if this would cause diverging package ecosystems.

We discussed an example of this at the meeting, with the assumption that the completion value slot is filled in a well defined way. `unless` would write to `a`'s completion...

I'd note the result is not implementation defined, per https://tc39.es/ecma262/#sec-try-statement-runtime-semantics-evaluation invoking [UpdateEmpty](https://tc39.es/ecma262/#sec-updateempty)(C, undefined).

@TzviPM I think https://tc39.es/ecma262/#sec-ecmascript-function-objects-call-thisargument-argumentslist might be what you are meaning to get to at 10.2.1.10 ?

@TzviPM correct, though I don't know of an engine that allows for it to do so even with exotic host objects.