3 ms·

That's strange, what's the motivation behind not allowing destructuring? Seems very prudish.

• masklinn 3y ago
  It's ambiguous. Are you disposing of the object being destructured or the destructuring results? How do you make the distinction? Much easier to not do it.
  • wruza 3y ago
    Not sure if this would produce more issues, but they could ignore c# and use something like: const using x = getX() const {using prop1, prop2} = using getX() void using getX() // x, prop1 and 2 anonymous Xs to dispose Instead of giving `using` the power / the burden of variable creation. This also solves `using mutex.lock()` mentioned elsewhere itt.
  • saiojd 3y ago
    To me it seems like disposing of the object being destructured is the natural solution. But I can see where others will disagree.