On Saturday, 19 April 2014 at 17:51:38 UTC, monarch_dodra wrote:
Also, I don't think statically pre-allocating the error is an acceptable workaround.
Just in case that's not clear, I mean for the generic "assert(...)". For throwing actual run-time exceptions, I think it's fine to require a static preallocation in an @nogc.
Though it does raise the issue of things such as global state (what if a catcher changes the msg?), exception threading, and finaly, purity.
Seems @nogc prevents both a the same time "can throw" and "pure" ... ?
