public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickhuang99 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104255] parsing trailing return type fails with parameter pack expansion when two parameter packs at present
Date: Thu, 27 Jan 2022 20:49:31 +0000 [thread overview]
Message-ID: <bug-104255-4-O47iqArvk7@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
--- Comment #1 from qingzhe huang <nickhuang99 at hotmail dot com> ---
Just a FYI, this version is a bit simplified from this original code.
(https://www.godbolt.org/z/n7ajzr46f) because this is an actual meaningful
function to reverse a given index_sequence. You can see if trailing return type
works, it doesn't need to define the function body so that the template
function works exactly like a meta function.
template<size_t...Indexes, size_t...Numbers>
auto get_reverse_sequence_helper(index_sequence<Indexes...>indexes,
index_sequence<Numbers...>numbers)
// If this trailing return type is OK, we don't need actually define
// function body.
->index_sequence< (getSeqByIndex<Indexes, Numbers...>(numbers))... >
{
return index_sequence< (getSeqByIndex<Indexes, Numbers...>(numbers))...
>{};
}
next prev parent reply other threads:[~2022-01-27 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 22:51 [Bug c++/104255] New: " nickhuang99 at hotmail dot com
2022-01-27 20:49 ` nickhuang99 at hotmail dot com [this message]
2022-01-28 15:11 ` [Bug c++/104255] " 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
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-O47iqArvk7@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).