public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alisdairm at me dot com" <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: Tue, 28 Mar 2023 20:07:33 +0000 [thread overview] Message-ID: <bug-98939-4-WRzFTzkQ7N@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 Alisdair Meredith <alisdairm at me dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alisdairm at me dot com --- Comment #9 from Alisdair Meredith <alisdairm at me dot com> --- Trying to make sense of the new C++23 deprecation in [depr.template.template], I came up with the following, based on Example 3 in [temp.names]p6: template <typename T> struct A { void f(int); template <typename U> void f(U); }; template <typename T> struct B { template <typename T2> struct C { }; }; // deprecated: T::C is assumed to name a class template: template <typename T, template <typename X> class TT = T::template C> struct D { }; D<B<int> > db; // recommended: T::C is assumed to name a class template: template <typename T, template <typename X> class TT = T::C> struct E { }; E<B<int> > db; Currently, the recommended form does not compile, which I presume is a change to become valid with P1787. Likewise, the deprecated form does not warn — but that is not surprising if the preferred form is not compiling yet! Hope the example is useful.
prev parent reply other threads:[~2023-03-28 20:07 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 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 [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-98939-4-WRzFTzkQ7N@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).