Comment #0 by verylonglogin.reg — 2012-05-24T03:39:44Z
Original NG thread:
True disposable objects (add "Finalized!" assertion)
http://forum.dlang.org/thread/[email protected]
First message from NG thread:
This idea is too obvious and I suppose I'm the only one not knowing it,
but I have never seen it's implementation. Why?
The idea:
1. `Object` class has hidden `isAlive` field which is true since
construction and up to finalization.
2. Every method asserts that the object is alive first.
3. There is an `finalize` function that just rt_finalize an object in
debug mode but can even free memory in release mode.
Isn't it no-brainer? Isn't it the only way to debug manual memory
management and shared resources without error-prone boilerplate?
This is what I missed in C#, where I can dispose an object but I have to
manually check the object isn't disposed every time I use it or in every
it's method to find where I'm doing something with a disposed object by
a mistake.
IMHO finding using of dead references is almost as major as not allowing
to free memory of alive objects (I mean GC), but GC is often implemented
and dead references detection isn't.
Strongly require your thoughts.
Comment #1 by alex — 2012-05-24T03:46:56Z
The idea in and of itself is not bad. In fact, it would make debugging wonderfully easy. My only concern is this: Object size. We already store two words of memory in *every single object header*. This means 8 bytes on 32-bit and 16 bytes on 64-bit.
Now suppose we added an extra bool field to Object. Not only would the compiler have to be changed to align fields correctly, but it would also result in objects eating 12 bytes on 32-bit and 24 bytes on 64-bit (simply because the GC only power of two allocations or something along those lines).
Now, the memory concern is not a problem for a class like this:
class A
{
bool b;
short s;
}
Obviously we don't need word alignment here, and we could probably optimize given that. But consider:
class B
{
A a;
}
Suddenly that bool field has to suck an entire machine word's worth of space for 'a' to be aligned correctly.
Comment #2 by verylonglogin.reg — 2012-05-24T04:00:11Z