This feels wrong

[Marc Schütz via Digitalmars-d]

It seems this is a natural consequence of the lowering. As such, 
I'm not surprised by the behaviour, of course under the 
assumption I - as an end user - actually know that the given 
opApply catches the exception. I guess there could be a 
recommendation in opApply's specification that implementors 
shouldn't needlessly catch exceptions, especially not unspecific 
ones like `Exception`, but if they do, they should rethrow them, 
or better yet use scope(exit/finally) and try/finally as 
appropriate.