None of this reply even has anything to do with what I asked, which was why you think you need a VM and garbage collection to run specific CPU instructions.
> All concurrent complex datatypes leak memory with C/C++
That's completely ridiculous and shows that you have a very fundamental misunderstanding of how these things work. They are wrappers around functions that do the atomic operations.
You were implying that atomic operations, which don't allocate any memory and are just a pass through to CPU instructions operating on a pointer, somehow leak memory.
Now you are saying "all concurrent maps" in C++ leak memory which not only has nothing to with what you said earlier, but it an insane claim to make without linking to specific maps you are talking about, not to mention that there aren't any in the C++ standard library.
> Please show some code you have written or stop replying to my comments.
What would make you realize that saying operations fundamental to a CPU "leak memory" is like saying 'loops make programs crash'. It is only something someone would say if they not only don't understand the fundamentals of what they are talking about, but don't even realize they don't understand it and in fact are absolutely sure that they do.
> All concurrent complex datatypes leak memory with C/C++
That's completely ridiculous and shows that you have a very fundamental misunderstanding of how these things work. They are wrappers around functions that do the atomic operations.
https://en.cppreference.com/w/cpp/atomic/atomic_store
Feel free to show me the memory leak you were talking about.
https://godbolt.org/