Ron Buckton
Ron Buckton
In a way you could consider disposable resources have the following implicit behavior: - If `Symbol.dispose` is present, `using` acts as if an implicit `[Symbol.enterContext]()` method exists (if not found)....
> However, I do hope to at least allow `[Symbol.dispose]()` to observe the most recently thrown error of the existing scope. This would enable use cases like db rollback as...
> This seems very uncompelling to me, usually no errors would mean that everything has succeeded fine. For the case of `indexedDB` specifically this is specifically from how transactions already...
The .NET example predates C#'s own addition of `using` and `await using` declarations. The exact same sample can be written as the following in C# 8.0 or later: ```cs //...
Or as follows, if you want to preserve the block scoping: ```cs // Create the TransactionScope to execute the commands, guaranteeing // that both commands can commit or roll back...
@rixtox I would suggest you read through https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-8.0/using#using-declaration if you would like to learn more about C#'s adoption of `using` declarations.
No, it has not. At least, nothing outside of any issues that have been posted in this repo.
I opened https://github.com/whatwg/html/issues/8557 to discuss this with WHATWG
On a related note, I've also opened https://github.com/nodejs/node/issues/45658 to discuss adoption in NodeJS as well.
This reached consensus during the June 2024 TC39 plenary session.