On Saturday, 25 August 2018 at 20:52:06 UTC, Walter Bright wrote:
I.e. a nothrow constructor now must call a throwing destructor.
This is not some made up example, it breaks existing code:
https://github.com/dlang/dmd/pull/6816
If I fix the bug, I break existing code, and apparently a
substantial amount of existing code. What's your advice on how
to proceed with this?
Deprecated message and allow it (nothrow and @safe\system checks)
for a year or two? Guaranteed destructor call is important enough
to actually bother with this IMO. Nothrow and other attribute
deduction could also be a temporary option.
