pasts VS ghost-collections

This was one of the original ideas behind pasts. I wanted to share data on a single threaded executor without using RefCell, so I created the Join struct api (renamed and redesigned many times). I'm curious what you think of that approach.

Pointing out that you're comparing apples to oranges. First off, that example isn't marked #[no_std], that means it will not work on no-std. It's not the same example. You need to define a panic handler, eh_personality and an allocator all of which are conviniently ignored in your linked example because it targets std instead of no-std. If you look at the actual equivalent example in pasts, it is actually not more boilerplate: https://github.com/ardaku/pasts/blob/stable/examples/timer.rs

Apart from that, I goofed around and implemented some collections on top, to test the ergonomics.

I read a while ago about a paper on a concept called GhostCell, and i believe it solves this problem in safe rust with zero runtime overhead. I just found this implementation, but I didn't have time to read it: https://github.com/matthieu-m/ghost-collections/blob/master/src/linked_list.rs Anyway, from my understanding, if you want to implement some sort of non trivial data structure in rust efficiency, you have to use a little bit of unsafe code. I believe this isn't the case thanks to GhostCell (if my understanding of the problem it aims to solve is correct)

In the tripod_tree container -- just a binary tree, really -- I exposed a cursor modeled after Rust's LinkedList Cursor.

GhostCell is powerful enough to implement doubly linked lists in safe Rust which is quite a feat. https://github.com/matthieu-m/ghost-collections

May I interest you in https://github.com/matthieu-m/ghost-collections ?

It's fairly complicated: https://github.com/matthieu-m/ghost-collections/blob/master/src/linked_list.rs

> I think linked lists are a great example of something that causes Rust's ownership model to fall apart. I've seen it done with tradeoffs, but it's something that you're best off implementing with pointers and unsafe blocks

It's worth checking https://plv.mpi-sws.org/rustbelt/ghostcell/ and https://github.com/matthieu-m/ghost-collections for an alternate approach that's currently being worked on.

Quite non-intuitive and it has yet to be proven 100% safe, plus it doesn't actually obviate everything you might want to do w/ potentially-aliased pointers, meaning that some desirable patterns are still off-limits - but it has the best chance of working out so far.

I managed to implement the basic operations of the LinkedList this way, as well as a full Cursor, then I hit a wall.