public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: James Dennett <james.dennett@gmail.com>
Cc: Piotr Wyderski <piotr.wyderski@gmail.com>, gcc@gcc.gnu.org
Subject: Re: The future of concepts
Date: Tue, 28 Jul 2009 14:48:00 -0000	[thread overview]
Message-ID: <4A6F0F84.8060504@verizon.net> (raw)
In-Reply-To: <18738acb0907280305n7ff7fc19x6f3867a87ff5bf86@mail.gmail.com>

James Dennett wrote:
> On Tue, Jul 28, 2009 at 3:01 AM, Piotr Wyderski<piotr.wyderski@gmail.com> wrote:
>   
>> Concepts have recently been removed from the C++0x Standard Draft.
>> Will the concepts branch be discontinued?
>>     
>
> I hope not.  Concepts will be "finished" and re-added to C++, and it
> would be immensely helpful in that effort if there were a version of
> g++ with stronger Concepts support than ConceptGCC had.
>
> -- James
>
>   
We need a gcc branch for concepts.  One of the major complaints on 
concepts and one of the major contributors to its being dropped is that 
there is no implementation experience.  There was no implementation of 
sufficient quality and availability to give compiler developers 
confidence and point to wrinkles in the definition and users time to 
learn and play.  It will take a good couple of years to get one working.

That leaves open the question of whether the ConceptGCC branch is the 
one.  I just don't know.  Maybe someone should start over.  I think aim 
for simplicity.  That was another issue I think: 
http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2009/n2906.pdf     
(Stroustrup)

Ed

  reply	other threads:[~2009-07-28 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 10:01 Piotr Wyderski
2009-07-28 10:05 ` James Dennett
2009-07-28 14:48   ` Ed Smith-Rowland [this message]
2009-07-28 16:22     ` Basile STARYNKEVITCH
2009-07-28 19:18       ` Jonathan Wakely
2009-07-31 21:40     ` Jason Merrill
2009-08-01  2:22       ` Ed Smith-Rowland

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=4A6F0F84.8060504@verizon.net \
    --to=3dw4rd@verizon.net \
    --cc=gcc@gcc.gnu.org \
    --cc=james.dennett@gmail.com \
    --cc=piotr.wyderski@gmail.com \
    /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).