Repository navigation
feat: expose Explicit Resource Management (using) - #15027
Merged
Merged
Conversation
Lightning00Blade
changed the title
using)
Lightning00Blade
force-pushed
the
exp-espl-res
branch
from
July 6, 2026 15:49
0b9fbd9 to
c009a31
Compare
Lightning00Blade
marked this pull request as ready for review
July 6, 2026 15:50
Lightning00Blade
force-pushed
the
exp-espl-res
branch
from
July 6, 2026 15:55
c009a31 to
4170f31
Compare
Lightning00Blade
force-pushed
the
exp-espl-res
branch
from
July 7, 2026 11:42
4170f31 to
1726854
Compare
Collaborator
|
Looks like the formatting fails. |
OrKoN
approved these changes
Jul 7, 2026
Lightning00Blade
enabled auto-merge (squash)
July 7, 2026 11:53
Merged
This was referenced Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Explicit Resource Management reached stage 4 with multiple vendors already supporting it (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/using#browser_compatibility).
Once tc39/ecma262#3000 is merged and part of the spec, we should make this publicly available.
Note: NodeJS v22 does not support the keyword
using.