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

[Vladimir Panteleev via Digitalmars-d]

On Tuesday, 10 May 2016 at 21:01:38 UTC, Jack Stouffer wrote:
> On Tuesday, 10 May 2016 at 17:46:17 UTC, Vladimir Panteleev 
> wrote:
>> because we can't know that the Monitor implementation doesn't 
>> throw / use the GC.
>
> Why not? Surely this information is available at compile-time?

Well, not really, because it's done via an abstract interface. 
See Object.Monitor in object.d.