nothrow by default

[rikki cattermole]

On 06/01/2020 3:27 AM, Ola Fosheim Grøstad wrote:
> On Sunday, 5 January 2020 at 13:56:14 UTC, rikki cattermole wrote:
>> On 06/01/2020 2:51 AM, Ola Fosheim Grøstad wrote:
>>> But how will it be faster if it doesn't recover on the spot?
>>
>> If you tell it to unwind, it won't.
>> The idea is to either assert out or return from the erroring function 
>> and let the parent figure it out.
> 
> But I think that the concern that people have is that the codegen will 
> generate landingpads for all stackframes that either catch exceptions or 
> call destructors. And that those landingpads make writing the code 
> optimization stages more difficult.

If you use nothrow, the unwinding option would be disabled, so none of 
that would be a problem.

But you would lose the ability unwind, I don't think we can do anything 
about that right now.