RFC: Change what assert does on error

[Paolo Invernizzi]

On Friday, 4 July 2025 at 08:31:03 UTC, Adam Wilson wrote:
> On Friday, 4 July 2025 at 08:19:23 UTC, Paolo Invernizzi wrote:
>> On Thursday, 3 July 2025 at 23:38:03 UTC, Adam Wilson wrote:
>>> On Thursday, 3 July 2025 at 10:19:18 UTC, Paolo Invernizzi 
>>> wrote:
>>>> [...]
>>>
>>> I can't hook debuggers up to code running on a remote server 
>>> that somebody else owns in a DC hundreds of miles away. 
>>> Therefore the only debugging data available is stack traces. 
>>> If the language prevents the emission of stack traces then I 
>>> get ... absolutely nothing.
>>>
>>> [...]
>>
>> And what is preventing you to ask your colleagues for nix core 
>> dumps or win mini dumps?
>>
>> /P
>
> Not allowed as they contain unsecured/decrypted GDPR or 
> similarly embargoed data. These dumps cannot be transmitted 
> outside the production environment. That rule has been in 
> effect since GDPR was passed. GDPR caused quite a bit of 
> engineering heart-burn at Microsoft for years.

I don't want to be too much pedant, so feel free to just ignore 
me ..

We operate (also) in EU, and I interact constantly with our 
external Data Protection Officer.

GDPR is a matter of just being clear about what you do with 
personal data, and have the user agreement to operate on that 
data for some clear stated (and justified) purpose.

Debugging software is for sure a pretty common target purpose, 
also because imply more secure production services. That can be 
for sure added in the privacy policy the user anyway needs to 
agree with.

But I can feel your pain in having to deal with, well, pretty 
dumb way of setting internal rules.

/P