Ron Buckton

> I'm not a huge fan of the name `Symbol.enter`, like in my suggestion in #159 I chose `Symbol.create` specifically because all it does it make a wrapper rather than...

I've been considering this for some time, and I'm still not convinced a `[Symbol.enter]` is necessary at this time and is better left as a follow on. Even if `[Symbol.enter]`...

> Does any browser actually implement `using` yet? I could not find any evidence that one does. If we are only considering transpiled "platforms" I would still request this change....

> There's always an option to have a new set of APIs instead of upgrading existing ones. Even if you upgrade existing APIs, none of the existing code using them...

> What if we just keep it a TypeScript feature instead of pushing it to JavaScript? Or just move forward without the `using` syntax, just add `DisposableStack` only. I did...

I have added https://github.com/rbuckton/proposal-using-enforcement to the agenda for the upcoming TC39 plenary.

There is also nothing that prevents a resource from being reusable. Connections can be reopened, tracing blocks can be reset, etc. Imagine a tracing scenario where you want to trace...

> > large number of nursery objects > > I understand your example, but I guess I think that "most of the time" the resources you care about are not...

I'll put together some concrete examples. I've seen this come up in MVVM (model-view-viewmodel), where the majority use case of an `@observe` may be field-like definitions, but there are also...

The workarounds for this both would be a poor developer experience: ```js // using `accessor` class MyViewModel { // NOTE: decorator application order is *very* important here. @observe @onSet(function(oldFormat, newFormat)...