On Fri, Jan 9, 2026 at 11:02 PM Thiago Macieira wrote:
>
> On Friday, 9 January 2026 19:29:39 Brasilia Standard Time Frederick Virchanza Gotham wrote:
> >
> > (3) Use std::atomic to let the compiler decide
>
> You can ask std::atomic if for this type it is lockfree.
>
> The fact that some implementations have a wrong answer is a QoI problem.


Not necessarily a QoI problem. You could call it a QoS problem. When
the committee decided that 'is_always_lock_free' can give a different
answer to 'is_lock_free', they opened the door to all manner of
trickery . . . . . . . such as jumping into libatomic instead of
placing cx16 in place. It should never have happened.