Future of memory management in D

[jmh530]

On Tuesday, 16 November 2021 at 22:38:13 UTC, IGotD- wrote:
> [snip]
>
> The Achilles heel of D and its memory management was never the 
> GC itself or GC/not GC. It was that D didn't separate raw 
> pointers from managed pointers as different types. If D had 
> done that, it would have many more options.
>
> This borrow checker implementation in D, I'm not sure what the 
> purpose is and I don't have the whole picture either.

I'm confused by this because it seems as if the managed C++ 
iterations from Microsoft do not have much traction. What is the 
benefit of different types for GC/non-GC pointers?