> volatile is good for thread coordination. He has a point, though. https://en.cppreference.com/w/cpp/language/cv https://en.cppreference.com/w/cpp/language/c

> volatile is good for thread coordination. He has a point, though. https://en.cppreference.com/w/cpp/language/cv https://en.cppreference.com/w/cpp/language/cv > Every access (read or write operation, member function call, etc.) made through a glvalue expression of volatile-qualified type is treated as a visible side-effect for the purposes of optimization (that is, within a single thread of execution, volatile accesses cannot be optimized out or reordered with another visible side effect that is sequenced-before or sequenced-after the volatile access. This makes volatile objects suitable for communication with a signal handler, but not with another thread of execution, see std::memory_order). Any attempt to refer to a volatile object through a non-volatile glvalue (e.g. through a reference or pointer to non-volatile type) results in undefined behavior.