Follow

Is there a dialect whose approach to memory management is similar to the borrow checker?

@mauve There was eg carp github.com/carp-lang/Carp but it does seem to be neither under active development nor very mature :/

@crowdagger Oh cool. It seems they still have regular updates to the core. Have you used it for anything before?

@mauve No, I just watched a conference video on it youtube.com/watch?v=BQeG6fXMk28 It's cool if it is still maintained, I might give it a look sometimes :blob_cat:

@mauve No. See: dai.ed.ac.uk/groups/aisoc/maga [the background make it unreadable...] 'One day a student came to Moon and said, "I understand how to make a better garbage collector. We must keep a reference count of the pointers to each cons." Moon patiently told the student the following story-

"One day a student came to Moon and said, "I understand how to make a better garbage collector...

[note: pure reference-count garbage collectors have problems with circular structures that point to themselves.]'

@mauve (You can't make cycling structures in Rust without at least one unsafe. So actually even doubly linked lists are unsafe. I am annoyed by this, but also... nobody in 2025 should be writing their own linked list code. Which is also why serious people still need to understand C at a deep level)

@mcr314 Yes, I am well aware of the tradeoffs between approaches to memory management.

Sign in to participate in the conversation
Mauvestodon

Escape ship from centralized social media run by Mauve.