RFC: Change what assert does on error

[kdevel]

On Friday, 4 July 2025 at 07:21:12 UTC, Jonathan M Davis wrote:
> [...] And of course, for each such piece of clean up code 
> that's skipped, the more invalid the state of the program 
> becomes, making it that much riskier for any of the code that 
> does run while the stack unwinds to log any information about 
> the state of the program.

Maybe it's a heretical question: What kind of software do you 
write?
Why does the program state matter at all? I think that the process
state may be corrupted as long as the "physical data model"
remains unimpaired, e.g. does not get updated by the corrupted
process. If the physical data model does not live in the process 
of
course.