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++/98939] [C++23] Implement P1787R6 "Declarations and where to find them" Date: Thu, 18 Nov 2021 20:05:15 +0000 [thread overview] Message-ID: <bug-98939-4-QwiZZppHRQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98939-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98939 --- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Does that mean that code like this (from type_traits) needs to be fixed? class __make_unsigned_selector_base { protected: template<typename...> struct _List { }; template<typename _Tp, typename... _Up> struct _List<_Tp, _Up...> : _List<_Up...> { static constexpr size_t __size = sizeof(_Tp); }; template<size_t _Sz, typename _Tp, bool = (_Sz <= _Tp::__size)> struct __select; template<size_t _Sz, typename _Uint, typename... _UInts> struct __select<_Sz, _List<_Uint, _UInts...>, true> { using __type = _Uint; }; template<size_t _Sz, typename _Uint, typename... _UInts> struct __select<_Sz, _List<_Uint, _UInts...>, false> : __select<_Sz, _List<_UInts...>> { }; }; when parsing the default template argument I can't know if it can be parsed right away or if I need to delay parsing (unless it's a simple literal, which in this case it isn't).
next prev parent reply other threads:[~2021-11-18 20:05 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 19:40 [Bug c++/98939] New: " jason at gcc dot gnu.org 2021-02-02 19:40 ` [Bug c++/98939] " jason at gcc dot gnu.org 2021-07-08 17:05 ` mpolacek at gcc dot gnu.org 2021-11-12 21:14 ` mpolacek at gcc dot gnu.org 2021-11-18 17:38 ` jason at gcc dot gnu.org 2021-11-18 20:05 ` mpolacek at gcc dot gnu.org [this message] 2021-11-18 21:59 ` ppalka at gcc dot gnu.org 2021-12-03 5:02 ` pinskia at gcc dot gnu.org 2021-12-03 20:41 ` jason at gcc dot gnu.org 2021-12-04 11:38 ` pinskia at gcc dot gnu.org 2022-02-28 14:55 ` mpolacek at gcc dot gnu.org 2023-03-28 20:07 ` alisdairm at me 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-98939-4-QwiZZppHRQ@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).