public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: Panagiotis Foliadis <PFoliadis@hotmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [GSoC 2023] Rust front-end: Improving User Errors
Date: Tue, 21 Mar 2023 22:22:58 +0100	[thread overview]
Message-ID: <ri6o7olvlxp.fsf@suse.cz> (raw)
In-Reply-To: <AS2PR08MB883122E84209D57D01026DDDACBA9@AS2PR08MB8831.eurprd08.prod.outlook.com>

Hello,

 We are delighted you found contributing to GCC interesting.

On Mon, Mar 20 2023, Panagiotis Foliadis via Gcc wrote:
> Greetings,
>
> My name is Panagiotis Foliadis, Ι'm 26 years old and I am from Athens, Greece.
>
> I'm interesting in the Rust frοnt-end project and especially at Improving user errors. I'm a self taught 
> software developer with solid knowledge about Rust, and also Ι'm doing my internship that mainly uses C. I'm really 
> interested in the low level side of programming and especially compilers. I have already built gcc from source and 
> did some studying on the documentation to acquire some basic knowledge about the compiler.

Please note that Rust-GCC projects are a bit special in the sense that
they are often discussed primarily on Zulip of the gcc-rust team:

https://gcc-rust.zulipchat.com/

So you may want to reach out to them there as well.

>
> I'd like some guidance from the mentors prior to making a proposal, if there is any to give. 

I assume you have already read through https://gcc.gnu.org/wiki/SummerOfCode
The page has guidelines on what we expect to find a proposal.  Basically
you need to figure out what the project would entail and write it down,
with a little bit of detail and milestones.

Feel free to ask about any specifics either here on the mailing list or
on the Zulip linked above.

Good luck!

Martin

      reply	other threads:[~2023-03-21 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 19:55 Panagiotis Foliadis
2023-03-21 21:22 ` Martin Jambor [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=ri6o7olvlxp.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=PFoliadis@hotmail.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).