From: E M <micheletti.emanuele@hotmail.com>
To: "gcc-rust@gcc.gnu.org" <gcc-rust@gcc.gnu.org>
Subject: [GSoC] gccrs Unicode Support
Date: Fri, 31 Mar 2023 10:27:53 +0000 [thread overview]
Message-ID: <CEF8FBFB-CED5-4099-B5DA-29C43A296D79@hotmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Hi everyone!
My name is Emanuele, and I’m software engineer currently in my last MSc year.
I am writing to request your feedback on a proposal I written for this year’s GSoC.
I understand that my proposal may have come late, but I have tried to follow the feedback and recommendations of previous proposals to create as complete a version as possible.
My commitment can be full-time, I have finished my exams early, so I will be able to devote my time totally to this project to try to get a perfectly aligned solution.
https://docs.google.com/document/d/1Xlupkr6n973s9PCGjDsC03aTKQr0hn3MzltwYbK9AJY/edit#
Thank you very much!
Emanuele
next reply other threads:[~2023-03-31 10:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 10:27 E M [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-18 13:22 rust frontend and UTF-8/unicode processing/properties Mark Wielaard
[not found] ` <d5e7434b-80e8-2817-ed87-a23ef2ac0cbb@uma.es>
[not found] ` <CAOWUKr0Sd3RRSy2cuqMLj--KTWqOz=nQMxmx7ahM8YunrFzEig@mail.gmail.com>
2023-03-15 11:00 ` [GSoC] gccrs Unicode support Philip Herron
2023-03-15 14:53 ` Arsen Arsenović
2023-03-15 15:18 ` Jakub Jelinek
2023-03-16 8:57 ` Raiki Tamura
2023-03-16 9:28 ` Thomas Schwinge
2023-03-16 12:58 ` Mark Wielaard
2023-03-16 13:07 ` Jakub Jelinek
2023-03-18 8:31 ` Raiki Tamura
2023-03-18 8:47 ` Jonathan Wakely
2023-03-18 8:59 ` Raiki Tamura
2023-03-18 9:28 ` Jakub Jelinek
2023-03-20 10:19 ` Raiki Tamura
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=CEF8FBFB-CED5-4099-B5DA-29C43A296D79@hotmail.com \
--to=micheletti.emanuele@hotmail.com \
--cc=gcc-rust@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).