[oneshtein]

But even languages with Tricolour Mark&Sweep GC, which handles cyclic references just fine, it's still possible to make memory leak via a dangling reference to a node in a complex cross-linked graph, because language and GC allows that.

Rust by default forbids cyclic references, by forcing to use trees, which completely avoids the problem.

[LudwigNagasena]

You can leak memory in any complex project, even if you only use safe Rust.

Linux kernel uses doubly linked lists, Redis uses doubly linked lists, V8 JS engine uses doubly linked lists. Have their authors chosen something obviously wrong?

[oneshtein]

Rust uses double linked lists, they are not harder to implement in Rust than in any other language. Moreover, built-in borrow checker will help to implement them properly, without memory leaks or use-after-free. What is your point?

[LudwigNagasena]

My point is that it's not obviously wrong to create cyclic references.

[oneshtein]

OK, it's was obviously wrong to create cyclic references few years ago.

[LudwigNagasena]

But doubly linked lists use cyclic references…

[oneshtein]

Double linked lists use double links.