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++/106651] [C++23] P1169 - static operator()
Date: Mon, 12 Sep 2022 17:46:50 +0000	[thread overview]
Message-ID: <bug-106651-4-uRaEMhWXNj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106651-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 53565
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53565&action=edit
gcc13-pr106651-wip.patch

WIP patch which has parts of the changes implemented.
What is missing is [over.match.best.general]/1 and [over.best.ics.general]
changes and the library side, which means e.g. for the testcase from the paper:
struct less {
    static constexpr auto operator()(int i, int j) -> bool {
        return i < j;
    }

    using P = bool(*)(int, int);
    operator P() const { return operator(); }
};

static_assert(less{}(1, 2));
we ICE.
Testcase I've been playing with that compiles now:
template <typename T>
struct S
{
  static constexpr bool operator() (T const& x, T const& y) { return x < y; };
};

template <typename T>
void
bar (T &x)
{
  x (1, 2);
}

void
foo ()
{
  auto a = [](int x, int y) static { return x + y; };
  bar (*a);
  auto b = []<typename T, typename U>(T x, U y) static { return x + y; };
  b (1, 2L);
  S<int> s;
  s(1, 2);
}

  reply	other threads:[~2022-09-12 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 17:11 [Bug c++/106651] New: " mpolacek at gcc dot gnu.org
2022-09-12 17:46 ` jakub at gcc dot gnu.org [this message]
2022-09-13 13:18 ` [Bug c++/106651] " jakub at gcc dot gnu.org
2022-09-27  6:41 ` cvs-commit at gcc dot gnu.org
2022-09-27 11:00 ` cvs-commit at gcc dot gnu.org
2022-09-27 11:00 ` redi at gcc dot gnu.org
2023-03-07 19:34 ` cvs-commit 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-106651-4-uRaEMhWXNj@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).