dlang compiled app reported as trojan

[bachmeier]

On Sunday, 8 October 2023 at 18:59:01 UTC, Walter Bright wrote:
> Those malware detectors often flag non-Microsoft runtime 
> library code as malware. What it takes to fix it is to contact 
> the people who write the detectors.

They wouldn't even have to fix it. A starting point would be to 
give an honest error message like "Microsoft Defender has 
detected that this is potentially malicious software. If you 
don't trust the source, you should cancel the installation." 
Their message gives the impression that they've confirmed it to 
be malware even though they haven't. Given Microsoft's culture, 
it shouldn't be surprising they operate like that.