On Saturday, 17 June 2017 at 13:05:50 UTC, Adam D. Ruppe wrote:
The reason writeln fails @nogc is that it *might* throw an exception with most args if stdout is closed or something.

Perfect example of an *extremely* rare case failing @nogc's ridiculously strict requirements.

If that Walter's DIP about reference-counted exceptions gets trough it should ease problem like that quite a bit.

And as he said, memory-safe programming is not the problem -verifying the safety is. I think it is the same with GC.

Didn't Don Clugston say about something at some Dconf that it must trigger allocation "not hardly ever, NEVER"? So there's a real need even for the rigid @nogc, albeit a niche one.

Reply via email to