One global shared_ptr, two threads

Two threads share a single global std::shared_ptr<Widget> g_ptr (not std::atomic<shared_ptr<Widget>>, just a plain shared_ptr<Widget>). One thread runs g_ptr = std::make_shared<Widget>(...) to publish a new value; the other concurrently runs Widget copy = *g_ptr; to read the current one, with no external synchronization (mutex, atomic wrapper, etc.). Is this safe?

54 of 117 in C++