Kevin Gibbons

@rbuckton Sorry about that - esmeta is still a little imprecise. You should feel free to write the spec text you want and not worry about esmeta's errors, and we...

@rbuckton Noted, we'll get to it ASAP. If we don't get to it before the meeting you're welcome to ask for stage 4 pending editor review, and then assuming the...

I don't like that we have this degree of freedom. We should pick one and stick with it, and ensure the machinery only supports that kind. I'll prepare some PRs...

PRs: https://github.com/tc39/ecma262/pull/3605 / https://github.com/tc39/ecma262/pull/3606. I didn't do the actual changes to the ACs; that can wait until we decide which way we want to go. My preference is https://github.com/tc39/ecma262/pull/3606.

I approve this license change.

To be clear, the only observable change here is that if you have something like ```html eval('var x;') let x; ``` that is current an error (per spec), and with...

jmdyck points out that this undefines `sec-hasvardeclaration`, but I don't think there's really a good place for that to live now, so I'm OK with that.

It's not a typo. `!` means that _this particular call_ never throws. `! CreateDataPropertyOrThrow` means that the property creation is guaranteed to succeed. As to `! ReadableStreamDefaultControllerError`, see https://github.com/whatwg/streams/issues/1224 -...

> I don't think there's a risk of confusion about the attribute's purposes. I'm less concerned about purpose and more about how it's used: a hash and a public key...

This will need to be done for at least [Streams](https://streams.spec.whatwg.org/) as well, possibly other specs too.