public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickgray0 at brown dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99518] New: trailing requires clause adds nonexistent reference declarator to function parameter
Date: Wed, 10 Mar 2021 14:32:59 +0000	[thread overview]
Message-ID: <bug-99518-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99518
           Summary: trailing requires clause adds nonexistent reference
                    declarator to function parameter
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nickgray0 at brown dot edu
  Target Milestone: ---

the following code fails to compile

    #include <concepts>

    auto f(std::integral auto x) {}
    auto g(auto x) requires requires { { x }->std::integral; } {}

    auto main()->int {
        f(42); // OK
        g(42); // error
    }



error message: In function 'int main()':
<source>:8:9: error: no matching function for call to 'g(int)'
    8 |     g(42); // error
      |         ^
<source>:4:6: note: candidate: 'template<class auto:2> auto g(auto:2) requires
requires{{g::x} -> decltype(auto) [requires std::integral<<placeholder>, >];}'
    4 | auto g(auto x) requires requires { { x }->std::integral; } {}
      |      ^
<source>:4:6: note:   template argument deduction/substitution failed:
<source>:4:6: note: constraints not satisfied
<source>: In substitution of 'template<class auto:2> auto g(auto:2) requires
requires{{x} -> decltype(auto) [requires std::integral<<placeholder>, >];}
[with auto:2 = int]':
<source>:8:9:   required from here
<source>:4:6:   required by the constraints of 'template<class auto:2> auto
g(auto:2) requires requires{{x} -> decltype(auto) [requires
std::integral<<placeholder>, >];}'
<source>:4:25:   in requirements  [with auto:2 = int]
<source>:4:38: note: 'x' does not satisfy return-type-requirement, because
    4 | auto g(auto x) requires requires { { x }->std::integral; } {}
      |                                      ^
<source>:4:38: error: deduced expression type does not satisfy placeholder
constraints
    4 | auto g(auto x) requires requires { { x }->std::integral; } {}
      |                                    ~~^~~~~~~~~~~~~~~~~~
<source>:4:38: note: constraints not satisfied
In file included from <source>:1:
/opt/compiler-explorer/gcc-trunk-20210310/include/c++/11.0.1/concepts:102:13:  
required for the satisfaction of 'integral<decltype(auto) [requires
std::integral<<placeholder>, >]>' [with decltype(auto) [requires
std::integral<<placeholder>, >] = int&]
/opt/compiler-explorer/gcc-trunk-20210310/include/c++/11.0.1/concepts:102:24:
note: the expression 'is_integral_v<_Tp> [with _Tp = int&]' evaluated to
'false'
  102 |     concept integral = is_integral_v<_Tp>;

             reply	other threads:[~2021-03-10 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 14:32 nickgray0 at brown dot edu [this message]
2021-03-10 15:46 ` [Bug c++/99518] " nickgray0 at brown dot edu
2021-03-10 15:48 ` nickgray0 at brown dot edu

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-99518-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).