RFC: Change what assert does on error

[Richard (Rikki) Andrew Cattermole]

On 09/07/2025 8:17 AM, Dennis wrote:
> 1. `nothrow` currently affects code generation
> 2. `nothrow` currently affects whether `throw Error` skips finally 
> blocks in try-finally blocks
> 3. `nothrow` can be written down in source code or inferred, which is 
> treated the same
> 4. scope(exit) and destructor calls are lowered to try-finally, making 
> them behave equivalently
> 5. All this logic currently exists in the frontend
> 6. It is possible to remove the nothrow optimization by changing 
> frontend logic
> 7. There's a discussion going on whether that's desirable.
> 
> Do you disagree with any of these, or is there a different point you're 
> trying to make?

Different way of describing it, but for all intents in purposes we agree.