Future of D

IGotD- nise at nise.com
Sun Dec 13 22:18:26 UTC 2020


On Sunday, 13 December 2020 at 21:21:12 UTC, Max Haughton wrote:
>
> The problem with the GC is that it isn't optional. It is, 
> technically, but practically if you want to use the standard 
> library some things use the GC that really shouldn't.
>
> The solution will have to be better than C++. - passing 
> unique_ptr isn't good enough. In effect, this means we need a 
> combination of reference counting and borrowing. I understand 
> that this is a big task but we're a small but efficient 
> community so we should try.
>
> Garbage collection is absolutely a powerful tool but we 
> shouldn't lie to ourselves about where it doesn't fit.

D needs to differentiate managed and raw pointers, this has to be 
done in order to get out of the tracing GC swamp. Not a small 
task but I think that the D community can do it. This is the key 
and Nim has already gone through several types of GC in its 
development and keeps on updating them.

Also it would be nice to skip all the "unique_ptr" spamming in 
the source code like C++. A built in identifier would be nice 
like "int^ intPointer = new int;


More information about the Digitalmars-d mailing list