forcing "@nogc" on class destructors

[via Digitalmars-d]

On Wednesday, 21 January 2015 at 01:07:59 UTC, weaselcat wrote:
> On Wednesday, 21 January 2015 at 01:05:28 UTC, weaselcat wrote:
>> there is no silver bllet for memory and
> Sorry, meant "silver bullet for memory management", bit tired : 
> )

Yeah, but the silver bullet for memory management in real time 
applications are:

1. preallocation
2. O(1) allocation with upper bounds on total memory usage

Then you can use a GC if you
1. know when it runs and have headroom for it
2. can put an upper bound on what it scans

Implicit concurrent GC collection leads to:

1. less efficient codegen + restrictions related to FFI
2. higher memory usage with limited ability to put upper bounds
3. intermittent pauses
4. random cache pollution

Inconvenient if you try to get the most out of the hardware.