public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/10505 Date: Tue, 29 Apr 2003 17:06:00 -0000 [thread overview] Message-ID: <20030429170601.7740.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/10505; it has been noted by GNATS. From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: Wolfgang Bangerth <bangerth@ices.utexas.edu> Cc: gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/10505 Date: Tue, 29 Apr 2003 18:57:18 +0200 On Tue, Apr 29, 2003 at 09:25:19AM -0500, Wolfgang Bangerth wrote: > > [I guess we should continue in English and add this to the audit trail.] Yes we should. Here's an english summery of a private (german) diskussion with Wolfgang (partly reproduced by Wolfgang above): * The bug apparently needs --enable-concept-checks at compile time of gcc to trigger. [ Could the submitter please confirm this? g++ -v will hopefully tell the configuration options. ] * The basic question is: Is std::list<Foo> allowed to contain a field of type ``Foo'' (as opposed to ``Foo *'')? Basically this is what happens with the current list implementation if --enable-concept-checks is used. The program breaks because it tries to instantiate std::list with an incomplete type. * If the answer to the above is yes, the Bug is a user error. Otherwise it is probably a problem in the concept checks code. Note: The standard explicitly permits incomplete types as template arguments in an instantiation. regards Christian -- THAT'S ALL FOLKS!
next reply other threads:[~2003-04-29 17:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-29 17:06 Christian Ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-29 14:26 libstdc++/10505 Wolfgang Bangerth
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=20030429170601.7740.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).