From: gibix <gibix@riseup.net>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] [rust] Weekly report
Date: Sun, 20 May 2018 20:25:15 +0200 [thread overview]
Message-ID: <20180520182515.GA1130@nolla> (raw)
Hello!
Happy to share with you the first report of the gsoc's coding period.
https://gibix.github.io/2018/05/20/gsoc-week-1-report.html
I collected my first impression about writing CLIs with rust and how to
deal with errors. The links are a good collections of starting point for
those who wants to get their hands dirty with the language.
Have a good week
gbx
next reply other threads:[~2018-05-20 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-20 18:25 gibix [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-27 10:53 [gentoo-soc] [rust] Weekly report gibix
2018-05-12 18:03 gibix
2018-05-12 21:32 ` Luca Barbato
2018-05-13 16:04 ` bic
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=20180520182515.GA1130@nolla \
--to=gibix@riseup.net \
--cc=gentoo-soc@lists.gentoo.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