readerwriterqueue | fast single-producer , single-consumer lock | Reactive Programming library

std::thread objects are not copyable objects, the copy constructor is deleted:

TL;DR: As long as the implementation of ReaderWriterQueue<> uses atomic types with the correct memory orderings, you are fine.

The memory orderings that you need are memory_order_release on the writer side, and memory_order_acquire on the reader side. These memory orders imply, that all writes before an atomic write need to happen first, and that all reads after an atomic read need to happen later. These other writes/reads include your accesses to the data behind your ElemPtrs.

Since the queue itself needs to send data from one thread to the other, it needs to use the exact same memory orderings on its own atomic metadata to be able to send your payload data pointers. As such, you should be safe if the ReaderWriterQueue<> is implemented correctly.