public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106644] [C++23] P2468R2 - The Equality Operator You Are Looking For
Date: Sat, 22 Oct 2022 13:11:08 +0000	[thread overview]
Message-ID: <bug-106644-4-WfE5VmuitC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106644-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106644

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
As for implementation, I'd say in call.cc (add_candidates) we could do
something like:
  if ((flags & (LOOKUP_REWRITTEN | LOOKUP_REVERSE))
      && DECL_OVERLOADED_OPERATOR_IS (fn, EQ_EXPR))
    {
    }

before the loop on the overloads and depending on whether fn is in class scope
or namespace scope perform lookup (again argument dependent or not?) for
ovl_op_identifier (false, NE_EXPR) in the same scope.
But am not really sure what to do next if this finds something (supposedly in
the loop over the overloads?); I suppose if no template is involved, compare
the argument types (what else?), but for templates it is unclear (to me) if it
should try to instantiate them and compare types only afterwards, or what
exactly should be checked whether they correspond ([basic.scope.scope]).
Because e.g. http://eel.is/c++draft/basic.scope.scope#4.3.1 talks about
equivalent trailing requires clauses etc.

  parent reply	other threads:[~2022-10-22 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 16:27 [Bug c++/106644] New: " mpolacek at gcc dot gnu.org
2022-10-22 12:54 ` [Bug c++/106644] " jakub at gcc dot gnu.org
2022-10-22 12:57 ` jakub at gcc dot gnu.org
2022-10-22 13:11 ` jakub at gcc dot gnu.org [this message]
2022-10-25 11:34 ` jakub at gcc dot gnu.org
2022-11-04 19:37 ` jason at gcc dot gnu.org
2022-11-08  1:37 ` mpolacek at gcc dot gnu.org
2022-11-28 22:15 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106644-4-WfE5VmuitC@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).