public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104255] parsing function signature fails when it uses a function parameter outside of an unevaluated context
Date: Tue, 27 Feb 2024 05:12:52 +0000 [thread overview]
Message-ID: <bug-104255-4-qCzHZ0M7HK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104255-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104255
Barry Revzin <barry.revzin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry.revzin at gmail dot com
--- Comment #8 from Barry Revzin <barry.revzin at gmail dot com> ---
(In reply to Patrick Palka from comment #2)
> The error message is obscure, but it seems what GCC has issue with here is
> the use of the function parameter seq2 in the trailing return type occurring
> outside of an unevaluated context.
>
> I'm not totally sure if the testcase is valid
> (https://eel.is/c++draft/basic.scope.param#note-1 might suggest it's not?),
But we're not using the parameter for its "value" here (which I think means in
the sense of lvalue-to-rvalue conversion... as in reading a parameter of type
int), so I don't think this would be a reason to reject?
prev parent reply other threads:[~2024-02-27 5:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 22:51 [Bug c++/104255] New: parsing trailing return type fails with parameter pack expansion when two parameter packs at present nickhuang99 at hotmail dot com
2022-01-27 20:49 ` [Bug c++/104255] " nickhuang99 at hotmail dot com
2022-01-28 15:11 ` ppalka at gcc dot gnu.org
2022-01-28 18:48 ` [Bug c++/104255] parsing function signature fails when it uses a function parameter outside of an unevaluated context nickhuang99 at hotmail dot com
2022-01-28 22:40 ` nickhuang99 at hotmail dot com
2022-02-02 15:13 ` ppalka at gcc dot gnu.org
2023-10-06 13:42 ` ppalka at gcc dot gnu.org
2023-11-08 21:54 ` ppalka at gcc dot gnu.org
2023-11-08 21:55 ` ppalka at gcc dot gnu.org
2024-02-27 5:12 ` barry.revzin at gmail dot com [this message]
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-104255-4-qCzHZ0M7HK@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).