Jason Orendorff
Jason Orendorff
OK. To summarize this whole thread, the problem is: - we decided supporting relative module names is important - we decided supporting dynamic import (via the `Loader.prototype.import` API, not syntax)...
I don't know about _remove_; you may want to have heap types with fields of types you didn't define yourself.
Yup. There's: ``` //> 8. Let r be the result of evaluating mod.[[Body]]. ``` which is already not the right wording, but also that will be a Module parse and...
@dherman says: We removed it because of Promise.all, but you're right, it's pretty verbose :( Definitely could change. @dherman is taking this issue.
0d75da9 changed `PageSet` to use a linked list instead of a `Vec`.
Hooked up now—I had to implement a ton more builtins, including a fake `(values)` implementation. Have not written the test, though it should be easy.
Reopening. This is incomplete as long as there's no way to keep a ref alive across sessions. Right now, when you leave a session, everything in the heap is garbage,...
Still open until #29 is fixed.
Modules and scripts have different syntax (scripts eval synchronously, so they can't `import`) and semantics (a `var` in a module declares a variable that's local to that module, not a...
Yes we are going to propose dropping `loader.eval()` in favor of `realm.eval()`, but the issue still applies to `realm.eval()`. @dherman and I agree this is valuable and we want to...