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++/106179] [13 Regression] Rejected code since r13-1390-g07ac550393d00fca Date: Tue, 05 Jul 2022 21:27:38 +0000 [thread overview] Message-ID: <bug-106179-4-ZeZAkPOyMX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106179-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106179 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org --- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> --- The P1787 scope/lookup overhaul clarified that Mat_ in .operator Mat_ is looked up in the same way as a name mentioned immediately after the ., and since commaInitializer has dependent type _Tp, we don't know whether "Mat_" is supposed to name a member type of _Tp or the Mat_ in the enclosing scope, so we don't know if it's a template. Except that it has to be a type, so it has to be a template. So yes, it should work. As should this: template <class T> struct Mat { Mat(); }; //template <typename> struct Mat_; template <typename _Tp> Mat<_Tp>::Mat() { auto commaInitializer = _Tp().operator Mat_<_Tp>(); } struct A { template <class T> struct Mat_ { }; template <class T> operator Mat_<T>(); }; Mat<A> m;
next prev parent reply other threads:[~2022-07-05 21:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-04 9:42 [Bug c++/106179] New: " marxin at gcc dot gnu.org 2022-07-04 9:42 ` [Bug c++/106179] " marxin at gcc dot gnu.org 2022-07-04 9:46 ` redi at gcc dot gnu.org 2022-07-04 11:59 ` rguenth at gcc dot gnu.org 2022-07-05 21:27 ` jason at gcc dot gnu.org [this message] 2022-07-06 4:40 ` cvs-commit at gcc dot gnu.org 2022-07-06 4:40 ` jason at gcc dot gnu.org 2022-07-06 4:43 ` jason 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-106179-4-ZeZAkPOyMX@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).