Jack Works
Jack Works
I don't think do is a good name to use. Actually it increase the burden. You can not use it as the start of ExpressionStatement cause it will conflict with...
Yeah, actually I think we don't have to stick on the `do` keyword. Why not a new one just like in pattern matching. ``` `match` Block ``` For example, we...
And some of my friends usually think "do expression" is "do notation" (Haskell) in JS
That also removes the limit of do expression cannot appear as an ExpressionStatement strat
I strongly agree with `yield.received`
I have updated the issue to reflect the latest compartment API.
> Example: > > ```js > const x = new Compartment({ > // ... > importMetaHook(fullSpec, meta, moduleInsance) { > meta.url = fullSpec > meta.self = moduleInstance > } >...
```js const x = new Compartment({ // ... importMetaHook(fullSpec, meta, moduleInsance) { meta.url = fullSpec meta.self = moduleInstance } }) await x.import("/index") ``` > /index ```js export const x =...
> Is this what you are looking for? This is possible, but annoying to write. I just want to write those error inline.
I don't know, what's it seems like avoid shadowing is one of the main reason of introducing a new namespace. @hax can you explain?