A boolean is a non-negative integer with a maximum of one, often literally, but I see that calling the borrow checker a static reference counter with a maximum of one is frustrating you in the same way that you calling roc’s reference counting a garbage collector is frustrating me.
The string example is because the thing you’re calling runtime overhead is cheap compared to freeing up a string that’s been extended even just a couple of times. It’s not a trap. It’s an example where freeing the string itself could be considerably more expensive than the DEC c and BRZ that you’re calling overhead.
It’s a bit hypocritical to tell me off for not reading what you said when you haven’t bothered to figure out the relevance of the memory management examples I gave and just dismissed them out of hand as “rant” and a “trap”.
I haven’t read 90% of your comment since it is out of the topic of the discussion. The “trap” is trying to argue with mee about something I haven’t even mentioned.
A boolean is a non-negative integer with a maximum of one, often literally, but I see that calling the borrow checker a static reference counter with a maximum of one is frustrating you in the same way that you calling roc’s reference counting a garbage collector is frustrating me.
The string example is because the thing you’re calling runtime overhead is cheap compared to freeing up a string that’s been extended even just a couple of times. It’s not a trap. It’s an example where freeing the string itself could be considerably more expensive than the
DEC candBRZthat you’re calling overhead.It’s a bit hypocritical to tell me off for not reading what you said when you haven’t bothered to figure out the relevance of the memory management examples I gave and just dismissed them out of hand as “rant” and a “trap”.
I haven’t read 90% of your comment since it is out of the topic of the discussion. The “trap” is trying to argue with mee about something I haven’t even mentioned.