`@OTAtomicsThreadSafe` wrapper not usable on local var within a method about otatomics HOT 3 OPEN

i remember us talking about that at some point when i was wondering if you could use it inside a function. Didn't we decide the safe way was to wrap the wrapper var in a struct?

from otatomics.

It's mostly a paradigm shift - the concurrent code should do all its mutation externally, finish up, and return the final result synchronously within the method. But nothing should be concurrently mutating a local variable declared within the function.

A property wrapper is already wrapping the value, so adding more layers of wrapping won't really improve the situation. On the whole, there is no safe way to mutate a local var concurrently.

from otatomics.

That's where something like the operations library I've worked on come in handy (OTOperations, based on NSOperation). You can wrap concurrent work in a BasicOperation and execute it synchronously within a method if you choose.

And there's a host of other API that do similar things in the standard lib or otherwise. Again, just a paradigm shift.

from otatomics.