On 7 May 2015 at 23:39, Iain Buclaw <ibuc...@gdcproject.org> wrote: > When used properly though, it's properties make it a prime candidate > for the foundation of libraries/programs that centre around the use of > atomics. However, shared is not to be confused with a thread-safe > atomic type. Thread-safety is left to the end-user on such matters of > access. >
That last sentence should also include a mention of memory ordering too being left to the end-user.
