https://issues.dlang.org/show_bug.cgi?id=11574
Kenji Hara k.hara...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://d.puremagic.com/issues/show_bug.cgi?id=11574
monarchdo...@gmail.com changed:
What|Removed |Added
CC||monarchdo...@gmail.com
---
https://d.puremagic.com/issues/show_bug.cgi?id=11574
--- Comment #4 from Shammah Chancellor shammah.chancel...@gmail.com
2013-11-25 13:27:36 PST ---
I understand what's happening, but I don't think scope(failure) should ever be
used in this way. It's not what it was originally intended for,
https://d.puremagic.com/issues/show_bug.cgi?id=11574
--- Comment #5 from Shammah Chancellor shammah.chancel...@gmail.com
2013-11-25 13:30:08 PST ---
Also, see this -- scope(failure) unintentionally hiding an Error!
import std.stdio;
void someFunc()
{
scope(failure) { writeln(What?);} //
https://d.puremagic.com/issues/show_bug.cgi?id=11574
yebblies yebbl...@gmail.com changed:
What|Removed |Added
CC||yebbl...@gmail.com
---
https://d.puremagic.com/issues/show_bug.cgi?id=11574
--- Comment #1 from Shammah Chancellor shammah.chancel...@gmail.com
2013-11-22 20:10:22 PST ---
Created an attachment (id=1293)
Shows how scope(failure) return's can prevent proper exception bubbling.
--
Configure issuemail:
