From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Ed Smith-Rowland <3dw4rd@verizon.net>
Cc: James Dennett <james.dennett@gmail.com>,
Piotr Wyderski <piotr.wyderski@gmail.com>,
gcc@gcc.gnu.org
Subject: Re: The future of concepts
Date: Tue, 28 Jul 2009 16:22:00 -0000 [thread overview]
Message-ID: <4A6F25B6.1080702@starynkevitch.net> (raw)
In-Reply-To: <4A6F0F84.8060504@verizon.net>
Ed Smith-Rowland wrote:
> 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.
It could perhaps be not a branch, but a plugin, but I know not much
about C++ concepts, and absolutely nothing about the existing C++
concepts branch[es].
My belief is that making such code a plugin and not a branch would make
both the plugin feature and the experimental language feature (concepts)
more popular. And perhaps maintaining a plugin could mean less work than
maintaing an entire branch.
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
next prev parent reply other threads:[~2009-07-28 16:22 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
2009-07-28 16:22 ` Basile STARYNKEVITCH [this message]
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=4A6F25B6.1080702@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=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).