From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: Jason Merrill <jason@redhat.com>
Cc: James Dennett <james.dennett@gmail.com>,
Piotr Wyderski <piotr.wyderski@gmail.com>,
"gcc@gcc.gnu.org >> GCC" <gcc@gcc.gnu.org>
Subject: Re: The future of concepts
Date: Sat, 01 Aug 2009 02:22:00 -0000 [thread overview]
Message-ID: <4A73A6AE.10606@verizon.net> (raw)
In-Reply-To: <4A73646B.4010808@redhat.com>
Jason Merrill wrote:
> On 07/28/2009 10:47 AM, Ed Smith-Rowland wrote:
>> We need a gcc branch for concepts.
>
> Probably, if someone is working on them, just as for any ongoing project.
>
>> That leaves open the question of whether the ConceptGCC branch is the
>> one.
>
> No. Doug felt that much of ConceptGCC needed to be rewritten; the
> ConceptGCC branch is just a place to store the existing work for later
> reference.
That effort did look dead. It seemed to me like a clean slate would be
nice.
One idea I had was to look at the metaprogramming pseudo concepts that
seem to be in the library already and beefing those up. Maybe that plus
a tiny amount of core language secret sauce would be the best approach
for concepts.
>
> There is a cxx0x-concepts-branch, but no work has been done on it.
> Probably when someone starts serious work on reimplementing concepts
> we'll create a new branch. I don't currently have any plans to work
> on concepts, as there are plenty of other things to work on that will
> be in C++0x.
I agree. There's constexpr, lambdas, nullptr, etc.
Then there's library stuff like regex mostly.
I was thinking we'd have a lot of green check marks for most of C++-0x
when it finally comes out. I think other compilers will too. There
won't be hardly any latency at all between ratification and good and
broad support for C++-0x. That's nothing to sneeze at.
>
> Jason
>
prev parent reply other threads:[~2009-08-01 2: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
2009-07-28 19:18 ` Jonathan Wakely
2009-07-31 21:40 ` Jason Merrill
2009-08-01 2:22 ` Ed Smith-Rowland [this message]
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=4A73A6AE.10606@verizon.net \
--to=3dw4rd@verizon.net \
--cc=gcc@gcc.gnu.org \
--cc=james.dennett@gmail.com \
--cc=jason@redhat.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).