On 31.05.2012 20:30, David Nadlinger wrote:
On Thursday, 31 May 2012 at 10:22:04 UTC, Dmitry Olshansky wrote:
Or the make it the default, but do _allow_ proper stack unwinding (=
usual cleanup) after call to crashOnError(false).

This would render nothrow useless, at least if the current semantics of
it (throwing Errors is acceptable) are kept.

David

What are benefits of nothrow.
Aside from probably saving on codegen and documenting intent ?

--
Dmitry Olshansky

Reply via email to