So, having said that... I am completely in favour of removing class destructors. It's a simple principle. When you have to do less work, things can run faster. So I can see removing class destructors as a feature leading to reduced pause times. Destructors exist only for resource management. Doing resource management through GC... is a bad idea.
Removing class destructors would break my DQt library as it
currently stands, which wraps C++ classes with D classes, Qt uses
classes for polymorphism, for protected overrides and slots. I
would have to consider some other means of wrapping C++. It might
also be confusing for a few people.
- Re: More r... deadalnix via Digitalmars-d
- Re: More r... w0rp via Digitalmars-d
- Re: More r... ed via Digitalmars-d
- Re: More r... Paolo Invernizzi via Digitalmars-d
- Re: More r... Andrei Alexandrescu via Digitalmars-d
- Re: More r... Paolo Invernizzi via Digitalmars-d
- Re: More radic... deadalnix via Digitalmars-d
- Re: More r... Andrei Alexandrescu via Digitalmars-d
- Re: More radical ideas ... Nordlöw
- Re: More radical ideas about gc and ... ponce via Digitalmars-d
- Re: More radical ideas about gc and ... w0rp via Digitalmars-d
- Re: More radical ideas about gc... Andrei Alexandrescu via Digitalmars-d
- Re: More radical ideas about gc and ... fra via Digitalmars-d
- Re: More radical ideas about gc... Andrei Alexandrescu via Digitalmars-d
- Re: More radical ideas abou... monarch_dodra via Digitalmars-d
- Re: More radical ideas ... deadalnix via Digitalmars-d
- Re: More radical ideas ... via Digitalmars-d
- Re: More radical ideas about gc and ... Benjamin Thaut via Digitalmars-d
- Re: More radical ideas about gc... froglegs via Digitalmars-d
- Re: More radical ideas abou... Paulo Pinto via Digitalmars-d
- Re: More radical ideas about gc... Andrei Alexandrescu via Digitalmars-d
