<html>
<head>
<base href="http://bugzilla.gdcproject.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - _d_throw is not treated as `noreturn`."
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=207#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - _d_throw is not treated as `noreturn`."
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=207">bug 207</a>
from <span class="vcard"><a class="email" href="mailto:ibuclaw@gdcproject.org" title="Iain Buclaw <ibuclaw@gdcproject.org>"> <span class="fn">Iain Buclaw</span></a>
</span></b>
<pre>As for assert(0) in non-release code, it is still possible to catch it, so
there's not much in the way of optimising around that. :-)
I can have a look, but as far as I recall, gcc optimizer should treat it as
noreturn. Whether or not noreturn implies that everything in scope afterwards
is unreachable depends the optimizer too.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>