I have a class with an atomic member and i want to write a copy constructor:
struct Foo { std::atomic mInt; Foo() {} Foo(const Foo&am
No, if you don't know how it will be used, you should use memory_order_seq_cst to be safe. If you use memory_order_relaxed, you could run into issues with instructions being reordered.
memory_order_seq_cst
memory_order_relaxed