Suggestion: switch 'const' to 'using' where possible

[johndeighan]

I'm not sure if this is possible, but if so, that would be great:

When using either: const name = new SomeObject() or name := new SomeObject(), output using instead of const if the object has a [Symbol.dispose] key

That would ensure that an object's [Symbol.dispose] method is always called when the object goes out of scope.

[vendethiel]

Sadly Civet as it is has no idea about these. Plus these can trip up library writers

[edemaine]

I see a few possibilities:

1. A compiler flag makes all const into using. Performance penalty at the choice of the user.
2. A new :=-like shorthand for using. You'd have to be explicit, but at least it would be concise.
3. In a distant future where we have type-based overloading, we could maybe do as you suggest. But only if the type has the dispose.