On Saturday, 8 February 2014 at 11:17:26 UTC, Jakob Ovrum wrote:
On Saturday, 8 February 2014 at 11:05:38 UTC, Dmitry Olshansky
wrote:>
If both are thread-local and cached I see no problem
whatsoever.
The thing is the current "default" of creating exception is
AWFUL.
And D stands for sane defaults and the simple path being good
last time I checked.
How is it not a problem? XException's fields (message, location
etc) would be overwritten by the latest throw site, and its
`next` field would point to itself.
It's supposedly one exception instance per place where it can be
thrown, not per exception type. Then the problem would be
restricted to recursive calls, where in the exception handler for
XException, another XException is thrown.
