public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/33605] Comparable concepts cause errors with abstract types
Date: Mon, 01 Oct 2007 10:06:00 -0000	[thread overview]
Message-ID: <20071001100643.6500.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33605-13405@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pcarlini at suse dot de  2007-10-01 10:06 -------
The most recent boost release (1.34.1) of those checks uses the same code of
our adaption. Given that, and given of course that we are finally in the era of
real concepts in the core language for the forthcoming new standard, I don't
think we should change anything non-trivial in this area: in any case a
library-only solution will be always affected by serious problems.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33605


  parent reply	other threads:[~2007-10-01 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 22:42 [Bug libstdc++/33605] New: " gcc at david dot osborn dot name
2007-09-30 22:48 ` [Bug libstdc++/33605] " gcc at david dot osborn dot name
2007-10-01 10:06 ` pcarlini at suse dot de [this message]
2007-11-01 19:57 ` pcarlini at suse dot de

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=20071001100643.6500.qmail@sourceware.org \
    --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: link
Be 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).