this post was submitted on 15 Mar 2025
21 points (95.7% liked)

Rust

6697 readers
102 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS
21
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/rust
 

Question is how to do these in Rust. An example might be a browser DOM: each node has a parent pointer, a list of child pointers, left and right sibling pointers, maybe a CSS node pointer, etc. Inserting or deleting nodes has to repair the pointers to and from the neighboring nodes as needed.

I know this is doable since obviously Servo (Rust's initial driving application) has to do it. I hope the answer doesn't involve the word "unsafe". But I am quite unclear about how to create such a structure under Rust's rules of pointer ownership, and also how to reliably reclaim storage when nodes and trees/subtrees are deleted. Plus there will be thread safety rules that should be statically enforced if possible.

I've heard that doubly linked lists in Rust are handled by an unsafe library, yet this seems even worse. Thanks.

you are viewing a single comment's thread
view the rest of the comments
[–] livingcoder 4 points 2 weeks ago (1 children)

There are a few different ways to solve this problem without using unsafe and I'm not sure what would be considered idiomatic. Another option is to ultimately encapsulate all of the nodes in a reference-counted box like Rc or Arc and specify the type of your parent/child/sibling references to the same reference-counted box type. With that, you just share cloned instances around as needed.

The primary drawback here is that for mutable access you end up having to perform a lock every time on an underlying Mutex (or something similar). You also no longer have direct access to the singular instance of the node.

There are pros and cons to every approach.

[–] [email protected] 2 points 2 weeks ago (1 children)

Thanks. I might ask on irc how Servo does it. Given Servo's connection with Rust, it would be surprising for this to be too awkward.

[–] livingcoder 1 points 2 weeks ago (1 children)

Sounds good. Please share what you find and what you end up going with.

[–] [email protected] 2 points 2 weeks ago

I'm not trying to code anything right now. I'm just trying to understand Rust itself better, so I asked how its users deal with a particular problem. Thanks!