From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: Ed Smith-Rowland <3dw4rd@verizon.net>,
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 19:18:00 -0000 [thread overview]
Message-ID: <4348dea50907281218g4618973fs5ecb1827e3afea26@mail.gmail.com> (raw)
In-Reply-To: <4A6F25B6.1080702@starynkevitch.net>
2009/7/28 Basile STARYNKEVITCH:
>
> 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].
I don't think that would work - the standard library changes that go
along with the language feature could not be implemented as a plugin.
A branch seems like the right way to do it.
Jonathan
next prev parent reply other threads:[~2009-07-28 19:18 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
2009-07-28 19:18 ` Jonathan Wakely [this message]
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=4348dea50907281218g4618973fs5ecb1827e3afea26@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=3dw4rd@verizon.net \
--cc=basile@starynkevitch.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).