| 20:44 | <kriskowal> | I’ve made a rig to improve my understanding of the primitive.prototypeMethod() behavior empirically. My assumption proved false and that makes me more optimistic that a lexically scoped shared struct prototype registry could possibly maintain evaluator isolation https://gist.github.com/kriskowal/cd07cfcd93d79c1224c7036ca1e6c776 |
| 20:47 | <kriskowal> | That is, there could be a hook on a Module(source, hooks) constructor that would provide the prototype for a struct, like prototypeOf(source, keyOfSomeKind). |
| 20:48 | <kriskowal> | I believe nicolo-ribaudo was driving at that, and now I understand that it’s viable. |
| 21:01 | <nicolo-ribaudo> | I think that being able to completely virtualize that prototype attachment (i.e. have a hook for it) is neither needed nor desiderabile, but I'm happy to discuss it further :) |
| 21:01 | <nicolo-ribaudo> | By "not needed" I mean "not needed to maintain isolation" |