[explicit-resource-management] Add remaining tests specific to await using statement syntax
#4481
Conversation
| // This code is governed by the BSD license found in the LICENSE file. | ||
|
|
||
| /*--- | ||
| esid: pending |
There was a problem hiding this comment.
I don't think we should block the PR on this, but if you do have a chance I'd appreciate it if you could replace pending with the relevant HTML section anchor throughout the PR.
|
|
||
| $DONOTEVALUATE(); | ||
| async function f() { | ||
| await using x = null, y; |
There was a problem hiding this comment.
I was confused about where this is prohibited, but I figured it out eventually: it's in IsConstantDeclaration. Not a big deal, but it might be helpful to include that in the description or info in this and the following few tests.
| asyncTest(async function () { | ||
| await assert.throwsAsync(TypeError, async function() { | ||
| for (await using i = 0; i < 1; i++) {} | ||
| }); | ||
| }); |
There was a problem hiding this comment.
Should this not result in a SyntaxError, due to https://tc39.es/ecma262/#sec-let-and-const-declarations-static-semantics-early-errors?
| /*--- | ||
| esid: pending | ||
| description: > | ||
| await using: invalid assignment in Statement body |
There was a problem hiding this comment.
It'd be good to note in the info that the error is thrown in CreateDisposableResource
In an effort to make review more manageable, this extracts the remaining tests specific to
await usingstatement syntax from #3866