public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59790] Inner template class specialization has no direct access to outer template class typedefs Date: Thu, 05 Aug 2021 11:18:32 +0000 [thread overview] Message-ID: <bug-59790-4-YqWathswBn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59790-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59790 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- Fixed by r262637 and r262639 [PR c++/86374] Name lookup failure in enclosing template https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00701.html PR c++/86374 * pt.c (lookup_template_class_1): Use tsubst_aggr_type for contexts that are classes. PR c++/86374 * g++.dg/pr86374.C: New.
prev parent reply other threads:[~2021-08-05 11:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-13 16:04 [Bug c++/59790] New: " blaffablaffa at gmail dot com 2014-01-13 16:05 ` [Bug c++/59790] " blaffablaffa at gmail dot com 2014-12-14 0:51 ` ville.voutilainen at gmail dot com 2021-08-04 20:48 ` pinskia at gcc dot gnu.org 2021-08-04 20:51 ` pinskia at gcc dot gnu.org 2021-08-05 11:18 ` redi at gcc dot gnu.org [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-59790-4-YqWathswBn@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).