https://issues.dlang.org/show_bug.cgi?id=16972
--- Comment #3 from Vladimir Panteleev <[email protected]> --- Good find. A pertinent post from that thread: http://forum.dlang.org/post/1237688782434087169.692302seewebsiteforemail-erdan....@news.digitalmars.com Indeed, it seems facetious to "forbid" throw but allow calling non-nothrow functions, and enforcing the latter is likely to break too much code now. So, we need confirmation that the current compiler implementation is sane and deals with throws properly, after which the spec could be updated. --
