<https://github.com/Yardanico/website/blob/yard-arc-orc-article/jekyll/_posts/2020-10-14-what-are-arc-and-orc-in-nim.md>
Interesting. This helps me understand what's going on. I was a big fan of "owned refs", but I didn't follow the discussion last year. I wanted to wait for the feature to become available before diving in. Then ARC became the top choice. ARC is very nice. I'm still a fan. But I'm not sure it solves my main problem: To be able to avoid copies in multithreaded code without resorting to raw pointers. My usual model is to create a heavy datastructure in the main thread, and to use parts of it in worker threads. I had assumed that if my instance is not "var", then I could pass it into the thread as an alias, detected by ARC. But from reading the forum I think that it might be copied. This for me is the part that requires the most clarification. Maybe I need to wait for "owned refs" to be fully implemented? FWIW, I also loved the old "memory-regions", but that didn't solve my multi-threading problem.
