Mark S. Miller
Mark S. Miller
> ```js > JSON.stringify({"foo": 1, "bar": 1}, [new anotherRealm.String("foo")], new anotherRealm.Number(4)) > ``` Is this the example you meant? I just tried it in Chrome with and without `anotherRealm.` and...
What happens with these across transparent membranes? I have not yet tried that.
Assuming the JSON example does not work across membranes, the problem is the use of the object wrappers for primitive types. For strict code, this object wrapping never happens implicitly....
What I really care about is that the programmer is able to write a closed-enough strict function, send it through a communications path that stringifies, transmits the string, receives and...
@ljharb I'm responding to the question of what I really care about. To clarify, for my purposes, the lexical context needs to be one that a receiver can evaluate strings...
> Can you respond to my second point in #32 (comment) ? > Second, when evaluated in the proper lexical context - inside an object literal, in this case -...
> You wrap the string to be evaluated in the appropriate lexical context - which could also be sufficient to extract the method from the newly created object or prototype...
That's why the case I care about is a standardized receiving environment with the elements I enumerate at https://github.com/tc39/Function-prototype-toString-revision/issues/32#issuecomment-402523166 . Given Realms, this case actually is easy.
A general process issue I've been realizing lately is that we've all been trying to uphold unstated invariants, by reviewing and catching where proposals break those invariants. However, while these...