Jack Works

IIRC @hax has explained his reason to me in person. The main reason is, these kinds of values (extension methods, numerical literals, decorators, ...) are very specialized uses. This means...

@ljharb Hax's reason is applied across proposals (extension methods, numerical literals, decorators, ...). If my example confuses you, let me change my example to extension flavor. You can see how...

For anyone who struggled with this problem: Run this code before `regenerator-runtime` executes ```js globalThis.regeneratorRuntime = undefined ```

Yes, @mikecann You can run this code: ```js globalThis.regeneratorRuntime = undefined ``` Before regenerator is loaded.

The trick I mentioned only used to define the global variable and the instantiation of the object should be done by the regenerator-runtime. If any of your code runs before...

By wrapping all polyfills in the `declare` statements above, it can resolve the concerns I have mentioned at the meeting, that is, unused partially shimming doesn't cost anything. This also...

Does it mean when lookup a reference, it will go through this order? > globalThis \< (not accessible ) globalLexicals \< local scope

The problem with 2 separate hooks they're not in the same lexical context. ```js const a = module { export function a() a() } ``` Two separate hooks are not...

🤔 what about let's just built-in [immer.js](https://github.com/immerjs/immer)?

I don't think it's a problem. The [[Get]] (or [[GetOwnPropertyDescriptor]]) on the ModuleNamespace exotic object can trigger the module execution, so accessing a non-existed property should be able to trigger...