public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: Aaron Gray <aaronngray.lists@gmail.com>,
	GCC Development <gcc@gcc.gnu.org>
Subject: Re: Wanted: original ConceptGCC downloads / branch, concepts-lite branch
Date: Wed, 17 Aug 2022 22:22:49 +0200	[thread overview]
Message-ID: <CAH6eHdTuVnY2q-LbtUFmXoWvnYHLDwpNw6QxaL=H8pGM8n8-ng@mail.gmail.com> (raw)
In-Reply-To: <8333c102-ac9c-1a31-c500-8ac042b960d3@foss.arm.com>

On Wed, 17 Aug 2022, 16:20 Richard Earnshaw via Gcc, <gcc@gcc.gnu.org>
wrote:

>
>
> On 17/08/2022 12:42, Aaron Gray via Gcc wrote:
> > Hi,
> >
> > I am looking for the original ConceptGCC source code, the
> > https://www.generic-programming.org/software/ConceptGCC/download.html
> has
> > all broken links and the SVN is gone.
> >
> > Is this available on GCC git or SVN ?
> >
> > Also I am wondering if the original concepts-lite code is available too
> > anywhere please ?
> >
> > Also any pointers to the documentation for the current implementation ?
> >
> > Regards,
> >
> > Aaron
>
> Not withstanding what others have already said, the various concepts
> branches are still in the git repository, but aren't in the standard
> pull set.  You can use git fetch to explicitly pull them:
>
> d743a72b52bcfaa1effd7fabe542c05a30609614
> refs/dead/heads/c++-concepts




This is "concepts lite".


780065c813a72664bd46a354a2d26087464c74fc
> refs/dead/heads/conceptgcc-branch




I think this was Doug Gregor's work, but I don't know how much of
ConceptGCC is present on the branch.


ce85971fd96e12d0d6675ecbc46c9a1884df766c
> refs/dead/heads/cxx0x-concepts-branch
> 14d4dad929a01ff7179350f0251af752c3125d74



This is described at https://gcc.gnu.org/git.html as:

"This branch contains the beginnings of a re-implementation of Concepts, a
likely future feature of C++, using some of the code from the prototype
implementation on conceptgcc-branch. It is not currently maintained."

I don't know who did this work, check the git history.

  reply	other threads:[~2022-08-17 20:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 11:42 Aaron Gray
2022-08-17 12:16 ` Ben Boeckel
2022-08-17 12:29   ` Aaron Gray
2022-08-17 12:46 ` Jonathan Wakely
2022-08-17 12:55   ` Jonathan Wakely
2022-08-17 13:11     ` Aaron Gray
2022-08-17 14:19 ` Richard Earnshaw
2022-08-17 20:22   ` Jonathan Wakely [this message]
2022-09-04 17:25     ` Aaron Gray

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='CAH6eHdTuVnY2q-LbtUFmXoWvnYHLDwpNw6QxaL=H8pGM8n8-ng@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=Richard.Earnshaw@foss.arm.com \
    --cc=aaronngray.lists@gmail.com \
    --cc=gcc@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).