Allen Wirfs-Brock

Any ambiguities in addition to async function/method? While it's unfortunate to have such a special case, the easy solution would be to simply not allow async function declarations within a...

see https://github.com/tc39/ecma262/issues/832

>I'm also worried that much of the usage might be people writing own before methods for not much reason, just because they have to write it in many other places...

@littledan >The fact that you put own in front of all private methods in this proposal (even if you don't have a particular need for them to be different on...

>Any other usage scenarios? Well, I tried to suggest one via this example from the proposal: ```js class { own #callback(){} //a private instance method ... setCallback(f){this.#callback=f} } ``` This...

Currently, the object model defined by the private state proposal doesn't include the concept of private getters and setters, so a first step would be to extend that object model...

This behavior for [[Set]] was standardized by ES1 in 1997. Not something that can change.

@erights > Before we invent something complicated that would involve new semantic state, let's first ask whether we can simply fix the override mistake without breaking any actual programs. I...

@getify >JS has gone to a lot of trouble over the years to give the impression that its dynamic prototype system is -- or can be used as -- a...

I considered that possibility when I updated the algorithm to include the arguments environment. The reason I didn't go that route is that I wanted to emphasize that the separate...