And a real hero

In general, you are right. Once you explain to the borrow check you are doing the right thing then you have a fair level of confidence in it being right.

I think the point from the article is if it is worth it. Give the single sentence in the article about a list and pointer. There are various ways to do it safely (and ways to do it unsafely like you pointed out) and sometimes it might be ok to put the onus of that onto the developer and validated with valgrind, asans, and unit tests. For some this is far more enjoyable than worry about the borrow collector.

It’s all a trade off and it’s ok to have difference criteria when approaching a problem like a cli tool or even a business critical service. The problem becomes when Rust people claim that the borrow checker is the only way and we all roll our eyes.

But can you use tangled without bluesky? It doesn’t seem like you can right now.

Brave isn’t the answer….

Rolling fedora on the other hand is interesting

Reports from one guy who says he is a lifelong republican?

Exactly. It’s more like rough 30% of eligible voters. Fact is that roughly 47% didn’t vote.

How are you measuring memory storage size? Are you sure you are looking as resident memory size and not just the virtual memory size?

Actual storage of the structures should be nothing. Interfaces are “fat pointers” but that should really just be an extra word which node would have at least that if not more.

My guess is that if you are looking at virtual memory that more memory/garbage is produced in PARSING and not storing and that the virtual memory size allocated is high even after garbage collection but RSS should be different.

I take road trips in my EV. It’s fine. You get to pee and walk the dog. The extra time isn’t much and it’s actually way more relaxing