What would be needed to also support a threadsafe Arc-like?

[dlight]

I didn't find this in the docs so I thought about asking! Is cactusref's approach fundamentally incompatible with multithreading, or it's just that currently the implementation is focusing in single-threaded Rc?

[thefakeplace]

Also interested in this! Does the lib plan on implementing something like this?

[lopopolo]

Hey folks, thanks for reaching out and your interest in cactusref.

To start, yes, it should be doable to add an Arc equivalent to cactusref.

The existing cactusref::Rc and cactusref::Weak types are very heavily forked versions of alloc::rc::Rc and alloc::rc::Weak. The same approach in theory could be applied to std::sync::Arc.

There is an outstanding ticket to resync this repository's fork of alloc::rc with the upstream lib in rust-lang/rust:

• Resync Rc fork from upstream std #103

That work is probably the first step needed to consider adding an Arc equivalent. Additionally, I'd like to get miri and leaksan running in CI and passing on the Rc types before considering adding an Arc type.

Apologies for the lack of activity in this repository, cactusref has not been a priority for me or for Artichoke since it is nightly-only and not relevant to the ongoing mruby oxidation work.

If any of y'all would like to take a stab at this, I'd be more than happy to mentor.

[lopopolo]

I cut a ticket for the leaksan work here if anyone wants to pick it up:

• Add a LeakSanitizer workflow to CI #147