Lock-Free Rust: Crossbeam in 2019
Allow me to ask a dumb question:<p>At the end of the day, how can something that is safely concurrent also be lock-free?  At the lowest level, what is the primitive that enforces the safety, if it's not a lock or mutex?<p>My brain starts to run in cricles when I think of this scenario: two threads trying to write to one piece of data.  To do so safely, they need to take turns.  Therefore, one has to wait for the other to complete.  Therefore, one must acquire a mutually exclusive... hold on, that's a mutex!<p>Can someone please clear this up for me?