Worst ideas/features in programming languages?

russhy russhy at gmail.com
Fri Oct 15 15:46:39 UTC 2021


On Friday, 15 October 2021 at 14:24:16 UTC, SomeGuy wrote:
> On Friday, 15 October 2021 at 13:45:11 UTC, deadalnix wrote:
>>
>> Many D construct assume a GC. Which kinda is the point. Either 
>> you don't assume a GC and go the zig road, or you assume a GC. 
>> But D is trying to have its cake and eat it too, and the 
>> result is schizophrenic in nature.
>>
>
> This problem could still be solved by making the GC just 
> another allocator (and make it the default global allocator). 
> D's current GC only runs when an allocation is made anyway, so 
> doing this shouldn't break the behavior of existing code 
> (except leaking memory if the constructs that assume GC is 
> used, of course).
>
> Maybe from this point on those constructs can be made to use 
> reference counting instead and make sure they're 
> allocator-independent.

Yes i agree with you, that would make everyone happy and would be 
transparent without breaking any existing code




More information about the Digitalmars-d mailing list