...a problem.

I think having lazy GC, RAII, manual memory management and ref. counting would...

...the moment I do this:

#// handle wrapper, RAII
#class Command {
#	sqlite3_stmt* stmt;
#	~this() { sqlite3...

...much better than plain malloc/free).
[Note: RAII's auto = scope(exit)]
You would have...

...I don't find at all that RAII collection is "implicit" or "without writing any...

...be collected lazily? In other words, where raii or delete could not be applied appropriately?

...d at some appropriate point, or have raii applied to it. Classes with dtors that...

...for a dispose() pattern goes away ('delete'/raii takes over), expensive resources that should be...

...without writing any code", which covers both RAII and GC cleanup (if you're lucky...

...overlooked but the obvious ones, 'delete' and raii, now invoke the dtor whereas normal collection...

...a normal collection cycle. Invoking delete or raii just works as always, yet the invalid...