Allocator-aware @safe reference counting is still not possible

Dukc ajieskola at gmail.com
Tue Jan 24 15:03:46 UTC 2023


On Tuesday, 24 January 2023 at 14:51:06 UTC, Dukc wrote:
> I agree with you that we do not want to wait for any major 
> language-level changes, considering how long it took for 
> DIP1000 to become stable.

Also I suspect the benefit-to-complexity ration of `isolated` or 
a complete borrow checker would be poor. It fits Rust, since it's 
a dedicated systems programming language. D is an application 
programming and scripting language as much as it's a systems 
language, so for us it isn't as good fit.

After all, GC solves the majority of memory safety issues 
already, and DIP1000 can solve a big part, if not the majority of 
what isn't solved by the GC.


More information about the Digitalmars-d mailing list