https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122259
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2025-10-11
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>I understand g++ is trying to match match 'operator=', however, could it just
>use the expression "assign"?
Not really since it is about the overloaded assignment operator not being
matched.
I think leaving out the std:: part is missing the point of the reason why they
are there.
Maybe for an non matching operator= with const/volatile qualifier.
The wording could be:
assignment of const [volatile] variable/member cannot find the matching
operator=
The other reason why operator= are not match should be kept still. Especially
with the 2 (or more) levels diagnostic now which help with the association to
the non-matching operator=.
Plus with the json output (and html output) for diagnostic should allow for
much more complete diagnostic.
