public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98939] New: [C++23] Implement P1787R6 "Declarations and where to find them" Date: Tue, 02 Feb 2021 19:40:25 +0000 [thread overview] Message-ID: <bug-98939-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98939 Bug ID: 98939 Summary: [C++23] Implement P1787R6 "Declarations and where to find them" Product: gcc Version: 10.0 URL: http://wg21.link/p1787r6 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jason at gcc dot gnu.org Target Milestone: --- The changes from this paper should not affect a significant amount of code; many are clarifications that bring the wording in line with existing practice, some are clarifications of corner cases that most code doesn't depend on, like ambiguous lookup within a conversion-type-id. A few changes that allow code that has been ill-formed: conversion-type-id is added to the list of type-only contexts from P0634: template <class T> struct A { operator T::type(); }; // OK ::template is also not required in type-only contexts: template <class T> auto f(T t) { return static_cast<T::X<int>>(t); } // OK Default template arguments are now complete-class contexts, like default function arguments: template <class T> struct A { template <int I = sizeof(t)> void g() { } // OK T t; }; One change that might break a small amount of existing code: Since lookup for a name after . or -> now happens first in the scope of the object, .template is required in dependent.template X<...> even if a definition of X would be found by unqualified lookup. template <int> struct X { void f(); }; template <class T> void g(T t) { t.X<2>::f(); } // error, needs .template
next reply other threads:[~2021-02-02 19:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 19:40 jason at gcc dot gnu.org [this message] 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
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@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).