public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96170] New: Enhancement: allow requires-clause checking of statement expression substitution success or failure
Date: Sat, 11 Jul 2020 20:22:54 +0000	[thread overview]
Message-ID: <bug-96170-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 96170
           Summary: Enhancement: allow requires-clause checking of
                    statement expression substitution success or failure
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wjwray at gmail dot com
  Target Milestone: ---

Some sort of sfinae on statement expressions containing structured bindings
can provide a convenient way to detect the number of bindings in a type.

Checking in requires clauses seems like the most direct approach:
https://godbolt.org/z/Eoq9rr

    template <typename T> constexpr int arity()
    {
           if constexpr (requires (T& a) { ({auto [x] = a;}); })   return 1;
      else if constexpr (requires (T& a) { ({auto [x,y] = a;}); }) return 2;
      //   ... etc ... 3,4,5 ... N
      else
           return 0;
    };

G++ accepts the template and, 
for a type T that decomposes into 1 element, arity<T>() == 1 succeeds.

However, it fails eagerly on the 1st condition for any other type,
e.g. arity<int>(), arity<int[2]>(), &etc...

c.f. bug 92402 seeking to match Clang's ability to sfinae in other contexts

(Clang accepts the template above but returns 0 for all T.)

             reply	other threads:[~2020-07-11 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 20:22 wjwray at gmail dot com [this message]
2020-07-12 15:51 ` [Bug c++/96170] " wjwray at gmail dot com
2020-07-13 13:30 ` wjwray at gmail dot com

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-96170-4@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).