On Thursday, 17 April 2014 at 15:48:29 UTC, bearophile wrote:
Ola Fosheim Grøstad:
Where this falls apart is when you introduce a compacting GC
and the @nogc code is run in a real time priority thread. Then
you need both @nogc_function_calls and @nogc_memory .
Perhaps the @nogc proposal is not flexible enough. So probably
the problem needs to be looked from a higher distance to find a
smarter and more flexible solution. Koka and other ideas
appeared in this thread can be seeds for ideas.
Bye,
bearophile
Reason why @nogc is desired in general is because it is
relatively simple and can be done right now. That alone buts it
above all ideas with alternate GC implementation and/or major
type system tweaks.
It only needs some tweaks to make it actually useful for
common-enoough practical cases.
