On Thu, Apr 10, 2014 at 2:28 PM, Alex Crichton wrote:
> [1] -
> https://github.com/rust-lang/rfcs/blob/master/active/0003-opt-in-builtin-traits.md
Off topic, but sigh... first private fields, now this to add even more
verbosity to declaring a struct, which really should be a very low
friction th
Ra Ra Ooo La La !
Good work team !
(looking forward to the 64-bit snapshots)
On Thu, Apr 10, 2014 at 7:05 PM, Brian Anderson wrote:
> After a long time coming, the Rust windows bots are now running an
> up-to-date mingw-w64 toolchain. This was a very easy transition thanks to
> the efforts of
So this is happening now:
http://www.meetup.com/nyccpp/events/168545012/
It's the C++ meetup, but I'll be giving a short talk on rust. Please RSVP
before it fills up!
- Clark
On Wed, Mar 26, 2014 at 10:30 PM, Carter Schonwald <
carter.schonw...@gmail.com> wrote:
> I'm in NYC.
>
> ya'll shou
After a long time coming, the Rust windows bots are now running an
up-to-date mingw-w64 toolchain. This was a very easy transition thanks
to the efforts of our windows devs, including Vadim, Thad, and klutzy.
The practical impact of this is that windows developers should prefer
the mingw-w64 t
Much better 2nd response, Brian. More like a salesman. You want to pull
them in ... not push them away :-)
On Thu, Apr 10, 2014 at 2:01 PM, Brian Anderson wrote:
> Sorry for the curt response. The answer is that Rust is suitable for many
> of the same tasks as C. Thank you.
>
> Please do not h
Sorry for the curt response. The answer is that Rust is suitable for
many of the same tasks as C. Thank you.
Please do not have this discussion here.
On 04/10/2014 11:58 AM, Brian Anderson wrote:
Thank you for your interest, but this is not a constructive topic for
this venue.
On 04/10/2014 1
-g, or --debuginfo (0|1|2) will generate debuginfo. -g means
--debuginfo 2. see rustc --help for more details.
On Thu, Apr 10, 2014 at 8:13 AM, Artella Coding
wrote:
> Previously I would have debugged using the command "rustc -Z debug-info
> example.rs". However with Rust 0.11 nightly it does not
Thank you for your interest, but this is not a constructive topic for
this venue.
On 04/10/2014 11:35 AM, Jason Long wrote:
Hello Folks.
How are you?
I want to know something about Rust language and Is it C killer? I mean
is that in the future is it a replacement for C?
Cheers.
_
Previously I would have debugged using the command "rustc -Z debug-info
example.rs". However with Rust 0.11 nightly it does not work. What do I
replace the above command with? Thanks.
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org
Hello Folks.
How are you?
I want to know something about Rust language and Is it C killer? I mean is that
in the future is it a replacement for C?
Cheers.___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
Your BaseImpl enum isn't necessarily Send because it contains a trait
object (~Base). The typechecker doesn't know what type is behind this
trait object, so it doesn't know whether it's send or not. To make the
BaseImpl type Send again, you can change the definition to:
enum BaseImpl {
Since my last today gill fetch I have this error:
error: instantiating a type parameter with an incompatible type
`~BaseImpl`, which does not fulfill `Send`
for this code :
trait Base{}
struct SecondThink{
count2: int,
}
enum BaseImpl{
FirstThinkImpl(~Base),
SecondThinkImpl(~
Actually, I'd like to reiterate my original view that num::Zero should be
renamed to AdditiveIdentity (bear with me) based on the fact that when
mathematicians use the symbol 0 to denote additive identity, the symbol 0 is
not read "zero", but as "additive identity".
All the reasoning above appl
I trying to do some polymorphism with trait and object and I have some
problems.
At the beginning I want to store different types of object that
implement the same trait (Base) in a Vec. To do this I use the enum
pattern. If the enum contains only struct, I manage to iter the Vec for
the diff
A nice side-effect of using such a trait as a bound to the range argument type
A is that the meaning of iter::range(a, b) would become coherent (same
regardless of A) and more intuitive: returns a DoubleEndedIterator to all the
possible (and valid) values of type A in [a, b) in ascending order.
15 matches
Mail list logo
