[commandersaki]

I don't see how any of what you said makes Swift memory unsafe. Memory safety is about security, not about whether or not the program crashes, in fact you want a crash as opposed to continuing on which could admit corruption.

From that article I linked:

If you have conflicting access to memory from within a single thread, Swift guarantees that you’ll get an error at either compile time or runtime.

Does any of what you said lead to a vulnerability that can be exploited?