Beeflang garbage seeker/collector

[Basile B.]

On Friday, 23 February 2024 at 14:04:03 UTC, Daniel N wrote:
> On Friday, 23 February 2024 at 11:37:22 UTC, Basile B. wrote:
>> On Tuesday, 20 February 2024 at 16:40:28 UTC, Marconi wrote:
>>> In beeflang garbage collector (garbage seeker) do not clean 
>>> the memory, it only works in debug mode to help the 
>>> programmer find and fix memory leaks, double frees, etc. In 
>>> release mode, the program runs in full speed since there is 
>>> no garbage collector. I think this is the best approach about 
>>> memory management.
>>
>> Sounds peculiar. As far as I understand it's a way to verify 
>> if manual management is mastered. However, for a language that 
>> proposes manual management and on linux I'd just use valgrind. 
>> It's a useful tool when debug infos are also generated.
>
> I think it sounds like a clever solution, wish them the best of 
> luck. valgrind has enormous overhead, much more than normal 
> GCs. (Even ASAN has fairly large overhead.)

Sure, never wish someone to fail.

What I miserably failed to explain is that IMO this is not a GC, 
it's a tool.
Not bad, and actually useful, but dont call that a GC.