public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vince.a.bridgers at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94255] template specialization in different namespace causes crash Date: Sun, 22 Mar 2020 00:10:32 +0000 [thread overview] Message-ID: <bug-94255-4-xCz6R9087Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94255-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94255 --- Comment #1 from Vince Bridgers <vince.a.bridgers at gmail dot com> --- The corrected code successfully compiles. Basically, making sure the template specialization is in the correct namespace. namespace clang { class DynTypedNode { private: template <typename T, typename EnablerT = void> struct BaseConverter; template <typename T> struct ValueConverter {}; }; namespace ast_type_traits { using DynTypedNode = ::clang::DynTypedNode; }; // end namespace ast_type_traits }; // end namespace clang namespace clang { //namespace ast_type_traits { template <> struct DynTypedNode::BaseConverter<int, void> : public ValueConverter<int> {}; //}; // end namespace ast_type_traits }; // end namespace clang int main(void) { return 0; }
next prev parent reply other threads:[~2020-03-22 0:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-21 23:50 [Bug c++/94255] New: " vince.a.bridgers at gmail dot com 2020-03-22 0:10 ` vince.a.bridgers at gmail dot com [this message] 2020-03-22 4:15 ` [Bug c++/94255] " xerofoify at gmail dot com 2020-03-22 4:15 ` xerofoify at gmail dot com 2020-03-27 19:47 ` mpolacek at gcc dot gnu.org 2020-04-18 3:48 ` mpolacek at gcc dot gnu.org 2020-04-20 19:26 ` mpolacek at gcc dot gnu.org 2020-05-07 18:12 ` cvs-commit at gcc dot gnu.org 2020-05-07 18:12 ` mpolacek 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-94255-4-xCz6R9087Q@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).