Typical security issues in C++: why the GC isn't your enemy

[Commander Zot]

On Tuesday, 6 December 2022 at 03:13:41 UTC, Tejas wrote:
> On Monday, 5 December 2022 at 19:57:39 UTC, H. S. Teoh wrote:

> People will resort have to resort to `@nogc` stuff when writing 
> performance critical code anyways, so the protection from `D`'s 
> GC will go away in those cases; and Chrome engineers aren't the 
> kind of folk who will find the Rust learning curve to be steep.

This is just wrong. if you have performance critical code, you 
won't allocate in it. so you can just slap @nogc on it without 
problems.
the rest of your code can still use the gc just fine.