public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Feng <ef2648@columbia.edu>
To: StevenSun2021@hotmail.com
Cc: David Malcolm <dmalcolm@redhat.com>, gcc@gcc.gnu.org
Subject: Re: Re: GSoC: want to take part in `Extend the static analysis pass for CPython Extension`
Date: Mon, 3 Apr 2023 10:47:14 -0400	[thread overview]
Message-ID: <CANGHATXKW-DAVxX9zvhcaw1u61taCD5E5YcBmSUJDcdrmzpehQ@mail.gmail.com> (raw)

Hi Steven,

I’m happy to collaborate on this project together — it would be great
to have your experience with CPython internals on the team.

> And by the way, I can get to work long before the start-coding time point of GSoC timeline.


I can be involved in some capacity before the start-coding period as
well (I originally planned to spend the time getting well acquainted
so as to hit the ground running) but I would prefer if we leave the
more involved tasks (e.g reference count checking, format string
checking) to the start-coding time point as I can’t work in a full
time manner until late May due to commitments in school before then.
Perhaps we can begin with the more low hanging fruits such as
Error-handling checking, errors in exception handling, and
verification of PyMethodDef tables in the time before the start-coding
period? It might be good for us to start with these smaller tasks
first to be more efficient in tackling the more involved tasks
anyways. It would also be easy to divvy these tasks up as well.

Best,
Eric

             reply	other threads:[~2023-04-03 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 14:47 Eric Feng [this message]
2023-04-03 15:28 ` Martin Jambor
2023-04-04 14:31   ` Eric Feng

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=CANGHATXKW-DAVxX9zvhcaw1u61taCD5E5YcBmSUJDcdrmzpehQ@mail.gmail.com \
    --to=ef2648@columbia.edu \
    --cc=StevenSun2021@hotmail.com \
    --cc=dmalcolm@redhat.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).