[Issue 13055] @nogc std.string.sformat
https://issues.dlang.org/show_bug.cgi?id=13055 Iain Buclaw changed: What|Removed |Added Priority|P1 |P4 --
[Issue 13055] @nogc std.string.sformat
https://issues.dlang.org/show_bug.cgi?id=13055 Walter Bright changed: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=3248 --
[Issue 13055] @nogc std.string.sformat
https://issues.dlang.org/show_bug.cgi?id=13055 --- Comment #5 from Lodovico Giaretta--- Also, the current use of enforce inside sformat (which a comment states shall be removed) should be converted to an assert or something else that does not throw. --
[Issue 13055] @nogc std.string.sformat
https://issues.dlang.org/show_bug.cgi?id=13055 teddybear12...@gmail.com changed: What|Removed |Added CC||teddybear12...@gmail.com --- Comment #3 from teddybear12...@gmail.com --- Same problem ;/ --
[Issue 13055] @nogc std.string.sformat
https://issues.dlang.org/show_bug.cgi?id=13055 Timothee Courchanged: What|Removed |Added CC||timothee.co...@gmail.com --- Comment #2 from Timothee Cour --- ping. just ran into this again http://forum.dlang.org/thread/mailman.3496.1452412496.22025.digitalmar...@puremagic.com formatted assert error messages inside nogc functions --
[Issue 13055] @nogc std.string.sformat
https://issues.dlang.org/show_bug.cgi?id=13055 --- Comment #1 from bearophile_h...@eml.cc --- One of my intended usages for this function is to generate messages for exceptions in @nogc code. Chris Cain comments: It's just stack-allocated this way isn't possible since the exception can be thrown into a scope above your stack allocated chars. --