public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100612] std::jthread can't be initialized with a pointer to a member function taking a std::stop_token
Date: Sat, 15 May 2021 14:01:08 +0000	[thread overview]
Message-ID: <bug-100612-4-lwEJNMbTap@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100612-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The standard could support this by saying that if the function object is a
pointer to member function then the requirement is
is_­invocable_­v<decay_­t<F>, Arg0, stop_­token, decay_­t<ArgsN>...> where Are
is the first argument in the pack, and ArgsN is the rest of the pack. But
that's not what the standard says.

  parent reply	other threads:[~2021-05-15 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 12:32 [Bug libstdc++/100612] New: " jonathan.oconnor at protonmail dot com
2021-05-15 12:43 ` [Bug libstdc++/100612] " jonathan.oconnor at protonmail dot com
2021-05-15 13:58 ` redi at gcc dot gnu.org
2021-05-15 14:01 ` redi at gcc dot gnu.org [this message]
2021-05-15 14:02 ` redi at gcc dot gnu.org
2021-05-15 15:46 ` jonathan.oconnor at protonmail dot com
2021-05-15 21:15 ` redi at gcc dot gnu.org
2021-05-16 14:55 ` jonathan.oconnor at protonmail dot com
2021-05-17 13:31 ` redi at gcc dot gnu.org
2021-05-17 13:55 ` jonathan.oconnor at protonmail dot com
2021-10-01 19:40 ` cvs-commit at gcc dot gnu.org
2021-10-01 19:55 ` redi 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-100612-4-lwEJNMbTap@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).