/rustlings
Madhu
Date: Thu, 6 Jun 2013 22:11:45 -0700
From: catamorph...@gmail.com
To: danielmi...@gmail.com
CC: rust-dev@mozilla.org
Subject: Re: [rust-dev] Suggestions for small Rust programs for use in a
tutorial?
Jeaye,
Tim,
Not entirely sure if these are what you want, but bjz's
Hi all,
I'm currently working on slides for a Rust tutorial, that I'm going to
be presenting at Open Source Bridge in Portland in two weeks. I wanted
the tutorial to be driven by examples from real code, but I've had a
hard time finding examples that are both relevant, and self-contained
enough
On 06/06/2013 09:21 PM, Tim Chevalier wrote:
Hi all,
I'm currently working on slides for a Rust tutorial, that I'm going to
be presenting at Open Source Bridge in Portland in two weeks.
Tim,
Not entirely sure if these are what you want, but bjz's glfw-rs repo has
some basic examples of
On Fri, Jun 7, 2013 at 12:21 AM, Tim Chevalier catamorph...@gmail.com wrote:
Hi all,
I'm currently working on slides for a Rust tutorial, that I'm going to
be presenting at Open Source Bridge in Portland in two weeks. I wanted
the tutorial to be driven by examples from real code, but I've had
On Feb 4, 2012, at 1:17 PM, Patrick Walton wrote:
On 02/04/2012 06:21 AM, Arne Döring wrote:
The second suggestion is concerning tho #fmt macro. #fmt works like
printf, but its string is parsed at compile time, so that errors might
be thrown when the string is incorrect. So when you unwind
Hi
Maybe I should introduce myself first. I am Arne a Computer Science
student and my bachelor degree is not far away anymore. I am very
interested in new programming languages and lately I found out about
Rust. Because of the fact, that in the last time my most used language
is Scala I was kind
- Original Message -
From: Arne Döring kru...@googlemail.com
To: rust-dev@mozilla.org
Sent: Saturday, February 4, 2012 6:21:58 AM
Subject: [rust-dev] Suggestions
Hi
Hi, Arne.
Maybe I should introduce myself first. I am Arne a Computer Science
student and my bachelor degree
On 02/04/2012 06:21 AM, Arne Döring wrote:
The second suggestion is concerning tho #fmt macro. #fmt works like
printf, but its string is parsed at compile time, so that errors might
be thrown when the string is incorrect. So when you unwind this format
string at compile time, you know also all
