public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99833] [8/9/10/11 Regression] structured binding + if init + generic lambda = internal compiler error Date: Tue, 30 Mar 2021 20:58:21 +0000 [thread overview] Message-ID: <bug-99833-4-kUgpHS9Vlx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99833-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99833 --- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Reduced: namespace std { template <int __v> struct integral_constant { static constexpr int value = __v; }; template <typename> struct tuple_size; template <unsigned long, typename> struct tuple_element; template <long __i, typename _Tp> using __tuple_element_t = typename tuple_element<__i, _Tp>::type; template <typename...> class tuple; template <typename... _UTypes> tuple(_UTypes...) -> tuple<_UTypes...>; template <typename _T1, typename _T2> class tuple<_T1, _T2> { public: template <typename _U1, typename _U2> tuple(_U1, _U2); }; template <typename... _Elements> struct tuple_size<tuple<_Elements...>> : integral_constant<sizeof...(_Elements)> {}; template <unsigned long __i, typename _Head, typename... _Tail> struct tuple_element<__i, tuple<_Head, _Tail...>> : tuple_element<__i - 1, tuple<_Tail...>> {}; template <typename _Head, typename... _Tail> struct tuple_element<0, tuple<_Head, _Tail...>> { typedef _Head type; }; template <long __i, typename... _Elements> __tuple_element_t<__i, tuple<_Elements...>> get(tuple<_Elements...>); } // namespace std void f(auto x) { [&](auto...) { auto y = std::tuple{"", x}; if constexpr (auto [_, z] = y; requires { z; }) ; }(); } auto main() -> int { f(2); }
next prev parent reply other threads:[~2021-03-30 20:58 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-30 17:17 [Bug c++/99833] New: " nickgray0 at brown dot edu 2021-03-30 20:24 ` [Bug c++/99833] [8/9/10/11 Regression] " mpolacek at gcc dot gnu.org 2021-03-30 20:57 ` mpolacek at gcc dot gnu.org 2021-03-30 20:58 ` mpolacek at gcc dot gnu.org [this message] 2021-03-30 21:28 ` ppalka at gcc dot gnu.org 2021-03-31 7:56 ` rguenth at gcc dot gnu.org 2021-03-31 17:24 ` ppalka at gcc dot gnu.org 2021-04-14 9:40 ` jakub at gcc dot gnu.org 2021-04-14 9:54 ` jakub at gcc dot gnu.org 2021-04-14 10:36 ` jakub at gcc dot gnu.org 2021-04-14 11:14 ` jakub at gcc dot gnu.org 2021-04-14 12:25 ` ppalka at gcc dot gnu.org 2021-04-16 7:33 ` cvs-commit at gcc dot gnu.org 2021-04-16 7:35 ` [Bug c++/99833] [8/9/10 " jakub at gcc dot gnu.org 2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:53 ` [Bug c++/99833] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:53 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:11 ` jakub 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-99833-4-kUgpHS9Vlx@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: linkBe 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).