public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amewo22370 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108414] template meta programming
Date: Mon, 16 Jan 2023 07:00:13 +0000 [thread overview]
Message-ID: <bug-108414-4-lO4zOxWyjr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108414-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108414
--- Comment #2 from Евгений Лисицын <amewo22370 at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> > using nth_element_t = typename decltype([]<typename T>(const indexed<I, T>&){return std::type_identity<T>{};}(make_indexer<Ts...>()))::type;
>
> There are some known issue with lambda inside a decltype which seems like
> might be causing issues here ...
interesting that 'typedef' and 'using' have different behavior
next prev parent reply other threads:[~2023-01-16 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 6:30 [Bug c++/108414] New: " amewo22370 at gmail dot com
2023-01-16 6:40 ` [Bug c++/108414] " pinskia at gcc dot gnu.org
2023-01-16 7:00 ` amewo22370 at gmail dot com [this message]
2023-01-16 9:35 ` redi at gcc dot gnu.org
2023-01-16 9:40 ` [Bug c++/108414] Incorrect pack expansion as argument to lambda redi at gcc dot gnu.org
2023-03-27 10:13 ` yagreg7 at gmail dot com
2024-04-13 8:16 ` pinskia 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-108414-4-lO4zOxWyjr@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).