From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: Anastasia3412 <Anastasia3412@proton.me>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [GSOC] query about C++: Implement compiler built-in traits for the standard library traits
Date: Tue, 21 Mar 2023 23:34:23 +0000 [thread overview]
Message-ID: <CAH6eHdQ7d4hV9o816mXuxZ2qgeeMepcQKVTkosf3SP+-wOxjfQ@mail.gmail.com> (raw)
In-Reply-To: <ri6r0thvm9i.fsf@suse.cz>
On Tue, 21 Mar 2023 at 21:16, Martin Jambor wrote:
>
> Hello Anastasia,
>
> we are very happy that you are considering contributing to GCC.
>
> On Mon, Mar 20 2023, Anastasia3412 via Gcc wrote:
> > Hello Everyone I'm Anastasia.
> >
> >I am a prospective GSOC Student. I wish to know if the project C++:
> >Implement compiler built-in traits for the standard library traits is
> >still available. I have already build and got my hand dirty on
> >debugging GCC.
>
> Various prospective contributors have shown interest in it but we have
> not "promised" it to anyone, I don't think we can, so it is "available."
> It has been discussed for example here:
> https://gcc.gnu.org/pipermail/gcc/2023-February/240816.html
We already have two candidates working on it, before their proposal
has even been accepted. As a result, I think you'd have to be a very
strong candidate to get accepted for that project, and it might be
better to pick another one.
next prev parent reply other threads:[~2023-03-21 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 19:14 Anastasia3412
2023-03-21 21:15 ` Martin Jambor
2023-03-21 23:34 ` Jonathan Wakely [this message]
2023-03-23 5:47 ` Anastasia3412
2023-03-31 11:53 ` Martin Jambor
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=CAH6eHdQ7d4hV9o816mXuxZ2qgeeMepcQKVTkosf3SP+-wOxjfQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=Anastasia3412@proton.me \
--cc=gcc@gcc.gnu.org \
--cc=mjambor@suse.cz \
/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).