https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103933
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Óscar Fuentes from comment #4)
> Ok, thanks, but atomic<>::notify_(one|all) exist and show the problem, which
> was introduced as a "fix" for
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102994
Yes, I know. What exactly is the problem? If you call them on a non-const
object, it still works. No valid code is rejected as a result of those const
qualifications, except something very contrived that uses SFINAE of concepts to
fail if they also work on const objects.
I'm closing this as a dup of PR 102994, I don't see any advantage to having two
bugs about essentially the same thing.
*** This bug has been marked as a duplicate of bug 102994 ***
