https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102994
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- N.B. [member.functions] in the standard says "For a non-virtual member function described in the C++ standard library, an implementation may declare a different set of member function signatures, provided that any call to the member function that would select an overload from the set of declarations described in this document behaves as if that overload were selected." In general, being declared with a different signature is permitted. Do you have an example where a call to std::atomic<T>::notify_one() that should be valid according to the standard either fails to compile or misbehaves, as a result of being const qualified?
