Bug 3129 – Cannot take advantage of overriding Throwable.toString

It's a pain when you set Throwable.file, toString function is completely bypassed by catching block in tryExec, so you can't do posponed error message generation. AFAIK, only Error takes advantage of setting file field, so it makes sense to restrict default error output to instances of Error class. No need to worry about losing this functionality since equivalent code is already in Throwable.toString. dmain2.d, line 324 --- - if (e.file) + if (e.file && cast(Error)e) --- Another minor issue is that both Throwable.toString and tryExec iterate through nested exceptions and output trace contexts, so if file field is not set, both of them are executed resulting into duplication of exception info.

Another possible solution is to change line 320 --- - catch (Throwable e) + catch (Error e) --- so that unoverridden Throwable.toString is executed in catch(Object o) block.

Bug not reproducible.

Indeed, the code has greatly evolved since then and we can mark this as WORKSFORME.