D not considered memory safe

[Steven Schveighoffer]

On Monday, 1 July 2024 at 13:40:41 UTC, Brian Callahan wrote:
> ...at least according to Bleeping Computer: 
> https://www.google.com/amp/s/www.bleepingcomputer.com/news/security/cisa-most-critical-open-source-projects-not-using-memory-safe-code/amp/
>
> "Memory-unsafe languages are those that do not provide built-in 
> memory management mechanisms, burdening the developer with this 
> responsibility and increasing the likelihood of errors. 
> Examples of such cases are C, C++, Objective-C, Assembly, 
> Cython, and D."

It looks like that list comes directly from the CISA report. And 
it’s not exactly wrong, D is not safe by default. For example 
they don’t consider rust to be an unsafe language simply because 
you can use unsafe blocks.

D would I think need to be safe by default and use dip1000 by 
default to be appropriately labeled safe.

I’m still trying to find out more about the criteria, because I 
don’t think it discusses how languages were put into these 
buckets of safe and unsafe.

-Steve