On Saturday, 19 April 2014 at 18:05:48 UTC, Dicebot wrote:
In lot of standard library functions you may actually need to
allocate as part of algorithm, strict @nogc is not applicable
there. However, it is still extremely useful that no _hidden_
allocations happen outside of weel-defined user API and this is
something that less restrictive version of @nogc could help
with.
What you want is to mark some functions with @allow_gc ? So that
you only get GC where specified as a "contract"?
But isn't this more suitable for dynamic tracing/logging?
Because what you want is probably the frequency of GC allocations
in a particular call tree?
