Ron Buckton

I would probably have structured it as: ```ts export function setupSubscriptions(): Disposable { // localStack holds things allocated now using localStack = new DisposableStack(); // disposables holds things allocated later...

> unless I wrap it with another layer of `DisposableStack` like what I've been demonstrating in this issue. The interaction between disposables in your example is non-trivial given the disposal...

Yes, `using x = ...` behaves like `const x = ...` except that when the initializer runs, so long as the result is neither `null` nor `undefined`, the declaration captures...

`accessor` indicates a runtime transformation of a field to a `get`/`set` pair, and we don't currently allow `get` or `set` to be optional. Optionality is intended to indicate cases where...

I'm not quite sure how to address the remaining esmeta issues.

This last commit adds a few UpdateEmpty calls that aren't strictly necessary, but `esmeta` doesn't quite understand what's happening without it. I also had to switch AO parameters typed `:...

> @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...

Please note, I've created https://github.com/rbuckton/ecma262/pull/3 as a separate PR against this one containing the additional specification changes that would be necessary to support https://github.com/tc39/proposal-async-explicit-resource-management, should it advance to Stage 3.

I found an issue with the change in e4f2d05 to use an EE to restrict binding patterns, in that it results in an ambiguous parse of `using[x]` before the EE...

> I found an issue with the change in [e4f2d05](https://github.com/tc39/ecma262/commit/e4f2d05e10cfe77f9f7560cc6af5c26e072c445d) to use an EE to restrict binding patterns, in that it results in an ambiguous parse of `using[x]` before the...