HE Shi-Jun

> What if I want to "compose" two extensions? This is a high-level usage which mostly only used by advanced users, and u could always do composing in a separate...

> It's not just a tradition; it's an intentional design choice. @ljharb There are many "intentional" design in the past and cause ux problems --- as JS was intentionally designed...

@pitaj This specific rust example seems not good (because it could be simplified as `a?` and do not need `return`) Even consider similar usage in JS, it seems just ask...

One addition, `eval()` doesn't support `yield`. I guess it is based on the similar reason (cannot allow `yield` and meaningfully prohibit `return`). So it seems we should either support both...

@michaelficarra Could you give a code example to show how to provide protocol own states via decorator?

They are designed for common use cases. For constructors, the common use cases are reusing the prototype method. For namespace objects, the common cases are using the first argument as...

> Do `import ::{A} from 'a.js'` still expose the module itself as `this`? Yes. ```js // module m export function plus1(x) { return x + this.one } export const one...

@benburrill This is an interesting idea. I am not sure whether this idea was considered in the early days of generators. The generators of ES was borrowed from Python, and...

@benburrill > although raising an exception would be backwards incompatible, I personally don't think that should completely disqualify it. I also really want a way to deprecate some bad things...

@Justineo 是应该这样。本文只是列一个初步的结构。话说你知道有什么预处理器支持`@supports`的转换吗？