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
First, I like this a lot. I think applying it to operators as well is
definitely a good thing. I don't feel strongly about these closures
needing to copy the bound values. If you consider them a syntax for
currying, one would expect them to copy, but you could also look at
them as a shorthand for
- 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 is
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
On 2/4/12 1:50 PM, Patrick Walton wrote:
Here, assuming I understand your proposal correctly, the rule is
relatively simple: where there's an underscore, the lambda is always
positioned before the nearest parent PrimaryExpression. But with
operators, the rules become more complex. I don't know
