Is synchronized(...){...} doomed to never be nothrow/@nogc?

[Jacob Carlborg via Digitalmars-d]

On 2016-05-11 13:10, Walter Bright wrote:

> Perhaps instead of throwing an exception it can try to re-acquire at the
> lower level.

There is basically no lower level, except the low level abstraction 
which wraps the Posix or Windows call. But it might be that the code is 
not affected. It's actually calling Condition.wait and not Monitor.lock 
in the cases where it catches the exception.

-- 
/Jacob Carlborg