mm:sharedOrc

"Needed" is a strong word, it is not "needed" but it fills a void. `arc : atomicArc` corresponds to `orc : sharedOrc`. Practically speaking with sharedOrc we could remove the concept of "isolation" and "gc safety" from Nim. I know you all like "isolation" but I find it lacking and it's hardly u

mm:sharedOrc

Can you give the ELI5 of why yet another mm is needed? Would sharedORC be a replacement or an alternative for ORC?

Atena Labs CBD Gummies : Insider Truth-Nobody Tells You This

Product Review: —> Atena Labs CBD Gummies Used For: —> Support Anxiety & Stress, Chronic Pain Composition: —> Natural Organic Compound Side-Effects: —> NA Rating: —> ⭐ Availability: —> Online In recent years, the wellness industry has witnessed a surge in interest surrounding CBD products, w

Atena Labs CBD Gummies : Natural Solution to Relief Your Stress/ Anxiety

Atena Labs CBD Gummies : Natural Solution to Relief Your Stress/ Anxiety Atena Labs CBD Gummies Atena Labs CBD Gummies are a revolutionary product that has captured the attention of individuals seeking natural remedies for various health concerns. These gummies are infused with CBD, or cannabidi

Can I use OpenACC pragma in nim?

Unfortunately, the `||` iterator always prefixes by `#pragma omp`. With your example up there you get `#pragma omp acc kernels` above the annotated loop. I can only assume that it _[should](https://forum.nim-lang.org/postActivity.xml#should) be a relatively straightforward compiler fix to make

mm:sharedOrc

Ok, and true but =hooks are easy to do. I've been reading the FRC paper. Definitely intriguing.. Although it starts getting pretty complicated. The built-in concurrent read and possibly combining it with `{.cursor.}` seems awesome. Seems like a good fit for a shared-orc design overall.

mm:sharedOrc

Here is the implementation:

mm:sharedOrc

I was curious to find a YouTube talk on the algo. No luck, but this video from a Microsoft researcher mentions Nim!

mm:sharedOrc

`=hooks`on an object that uses `ptr` as a hidden field. However, not even that is required as in test programs and experiments it is usually easy enough to insert the `incRef/decRef` operations yourself.

mm:sharedOrc

> Our team of core developers does not have time to work on any of this, but > the algorithms can be implemented in Nim "userland" code via custom hooks on > top of Nim's unsafe ptr T construct. By that, you mean the `=hooks` on an object like shared pointers or just using raw pointers by thems

Fake Nim books an Amazon, which ones are real?

Another one: Nim: Mastering Nim Metaprogramming, Unleash the Power of Code Generation

mm:sharedOrc

"Somebody" should implement this paper: or maybe this one: FRC is super interesting as it has direct support for Nim's `var x {.cursor.}: ref T` idea making these memory safe as well 🙂. FRC

Can I use OpenACC pragma in nim?

Seems like that should work, you can always try with `--nimcache:./nimcache` to have Nim put the generated C files in a local folder so you can inspect them yourself. Be warned though, Nims C output isn't exactly pretty..