One thing to be careful of is that mutexes are fair, spinlocks are not. It is possible for a worker to wait indefinitely behind workers acquiring the lock at a later time.
[1]: http://joeduffyblog.com/2006/12/14/anticonvoy-locks-in-windo...
Also the article does indeed implement a real mutex (although a buggy one), not a spinlock. std::atomic::wait will use futexes (or whatever) underneath to genuinely put the process to sleep until it receives a wakeup.