public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108736] New: pconcepts] multidimensional subscript operator reports invalid error in requires test
Date: Thu, 09 Feb 2023 07:25:59 +0000 [thread overview]
Message-ID: <bug-108736-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108736
Bug ID: 108736
Summary: pconcepts] multidimensional subscript operator reports
invalid error in requires test
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ldalessandro at gmail dot com
Target Milestone: ---
The following code produces an error when evaluating the concept.
auto foo(auto a, auto... i) -> decltype(auto) {
if constexpr (requires { a[i...]; }) {
return a[i...];
}
else {
return a;
}
}
int x = foo(1);
> <source>: In instantiation of 'decltype(auto) foo(auto:1, auto:2 ...) [with auto:1 = int; auto:2 = {}]':
> <source>:10:12: required from here
> <source>:2:31: error: built-in subscript operator without expression list
> 2 | if constexpr (requires { a[i...]; }) {
> | ~^
> Compiler returned: 1
Workaround: specialize on sizeof...(i) to avoid this test when i... is empty.
Live example: https://godbolt.org/z/K3oezd1qz
next reply other threads:[~2023-02-09 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 7:25 ldalessandro at gmail dot com [this message]
2023-02-09 18:51 ` [Bug c++/108736] [concepts] multidimensional subscript operator inside requires with variable template arguments is broken pinskia at gcc dot gnu.org
2023-09-24 18:52 ` ppalka 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-108736-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).