James M Snell

FWIW, the key use case I'm thinking about here are host-defined objects with a wrapping JS object and an internal underlying C++ object. Specifically, can we safely dispose of the...

Another quick clarification, I assume the following is also true... ``` function foo() { using xyz = bar(); return promise.then(() => { // xyx captured by closure will have been...

@juner: > Shouldn't we leave using to the caller as above...? Generally, yes, but ... Misbehaving Code :-)

Really appreciate the responses, all super helpful. What I imagine from all of this is likely a new range of linter rules that help catch the problematic patterns and promote...

Ok. The reason I ask is that I'm currently looking at designing and implementing an overhauled, modernized socket API in Node.js with an eye towards implementing that also in Workers...

FWIW, one of the primary reasons Node.js defaults `allowHalfOpen=false` is to prevent resource leaks in the common case on the client side (e.g. for instance, if the user forgets to...

Strongly recommend taking things through a proper deprecation cycle on stuff like this.

We ought to be able to get very close. There will likely be some edge cases or options that we're not able to support, but for the most part it...

@fhanau @dom96 @garrettgu10 ... would like to get this landed soon to unblock @IgorMinar's team. Can I ask one of y'all to do a quick review on this?

Moved to draft. The fixups cause some test failures I'll need to investigate