In conclusion, stack allocation must be destroyed

[FeepingCreature]

On Tuesday, 19 July 2022 at 17:44:29 UTC, Walter Bright wrote:
> On 7/18/2022 5:13 AM, FeepingCreature wrote:
>> Stack allocation without extremely reliable escape analysis is 
>> an express ride to corruptiontown. And D does not have 
>> extremely reliable escape analysis.
>
> I have submitted open PRs to fix the known problems with it.

No yes, I know, and I'm not complaining per se. I'm just saying 
that I, personally, writing for a corporate usecase, would very 
gladly sacrifice a bit of performance for having confidence that 
I won't update the compiler and suddenly instead of version 1.0 a 
service sometimes chooses to report its version as -376789630.0. 
(To pick an example that was luckily caught in testing.)

New, even false, compiler errors and breaking libraries is 
completely fine with me. Deprecations: completely fine. 
Regression miscompilations, however, are the stuff that 
nightmares are made of. After all, compiler errors annoy 
developers; with a bit of bad luck, miscompilations annoy 
customers.