public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/47380] New: concept checking and incomplete types Date: Thu, 20 Jan 2011 16:37:00 -0000 [thread overview] Message-ID: <bug-47380-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47380 Summary: concept checking and incomplete types Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: marc.glisse@normalesup.org The following code compiles fine in normal mode, but not with -D_GLIBCXX_CONCEPT_CHECKS, which basically thinks the types are incomplete. Is this a known limitation? (by the way, the relevant doc still says C++0x will have concepts) #include <map> template<typename T, typename U> struct A; template< typename T> struct B { typedef A<T,B> Handle; std::map<int,Handle> y; }; template<typename T, typename U = B< T> > struct A : U { }; int main(){ A<int> x; }
next reply other threads:[~2011-01-20 15:49 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-20 16:37 marc.glisse at normalesup dot org [this message] 2011-01-20 18:13 ` [Bug libstdc++/47380] " paolo.carlini at oracle dot com 2011-01-20 18:14 ` redi at gcc dot gnu.org 2011-01-20 18:52 ` paolo.carlini at oracle dot com 2011-01-20 20:06 ` marc.glisse at normalesup dot org 2011-01-20 20:16 ` redi at gcc dot gnu.org 2011-01-20 20:18 ` redi at gcc dot gnu.org 2011-01-20 20:42 ` redi at gcc dot gnu.org 2011-01-20 20:44 ` marc.glisse at normalesup dot org 2011-01-20 20:47 ` redi at gcc dot gnu.org 2011-01-21 1:02 ` paolo.carlini at oracle dot com 2011-08-23 15:37 ` marc.glisse at normalesup dot 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-47380-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).