On Tuesday, 19 February 2013 at 07:36:43 UTC, Dicebot wrote:
This is unreasonable. D targets itself as a system programming language, among the others usage cases, and thus request to have a compiler-enforced memory usage guard is perfectly valid. What shall it do if something "fancy" is attempted in @nogc? Issue a compile-time error, profit!
I have nothing against @nogc. It seems to be a nice idea. I would like to see a way to "talk to GC" in D.
What I'm saying is things seem not to be that bad right now.
