In the Effective Java book, it states: The language specification guarantees that reading or writing a variable is atomic unless the variable is of type long or double [JLS, 17.4.7]. What do...

0 Since std::atomic_init has been deprecated in C++20, here is a reimplementation which does not raise deprecation warnings, if you for some reason want to keep doing this.

Reads and writes are atomic, but you also need to worry about the compiler re-ordering your code. Compiler optimizations may violate happens-before relationship of statements in your code.

I am intending to declare a vector of atomic variables to be used as counters in a multithreaded programme. Here is what I tried: #include <atomic> #include <vector> int main (void) { ...

The atomic "thing" in shared_ptr is not the shared pointer itself, but the control block it points to. meaning that as long as you don't mutate the shared_ptr across multiple threads, you are ok. …

reference assignment is atomic so why is Interlocked.Exchange (ref Object, Object) needed? Reference assignment is atomic. Interlocked.Exchange does not do only reference …

Can you use a std::atomic_bool to ensure mutual exclusion in a code block? Yep. std::atomic_bool is sufficient to implement a spinlock, which is simpler (although also less …

But rename() is still atomic in a very important sense: if you use it to overwrite a file, then you will end up with either the old or the new version and nothing else. [update: but as @jonas-wielicki …

The standard does not specify if atomic objects are lock-free. On a platform that doesn't provide lock-free atomic operations for a type T, atomic<T> objects may be implemented using a …

4 C++20 includes specializations for atomic<float> and atomic<double>. Can anyone here explain for what practical purpose this should be good for?