Hello,
since a few days, I have a lot of new errors in the master compiler. For
example in the rust_zmq lib that I use. When I compile it I have these
errors :
321:9 error: last argument in `do` call has non-procedure type: |*i8| -
V3
`do` no longer works with stack closures. It now only works with the new proc()
type, which basically means you're only going to see it used with spawn().
You need to now say something like
let rc = endpoint.with_c_str(|cstr| {
unsafe {smq_bind(self.sock, cstr)}
});
I can't
Thank you it correct my first problems.
I didn't send code because I thought it has the same cause. For the last
problems the code is :
use extra::serialize;
use extra::json::{Json, Decoder, ToJson, Object, Encoder, Decoder};
use extra::treemap::TreeMap;
use std::io::Decorator;
//second
I found my error. It's a classical problem.
TestStruct2 implement the trait `extra::serialize::Encodable` using the
generated impl by the compiler.
I didn't declare : use extra::serialize::Encodable;
So the compiler doesn't find it and declare the problem at the
implementation.
It's the same
No, since it isn't known which trait the method should come from. It
could list *all* the traits that provide that method with that
signature, but even that wouldn't be great if you had the signature
off.
On Thu, Dec 5, 2013 at 3:26 PM, Philippe Delrieu
philippe.delr...@free.fr wrote:
I found my
Perhaps the error message can be more explicit like trait not found for
method instead of method not found.
Le 05/12/2013 21:57, Corey Richardson a écrit :
No, since it isn't known which trait the method should come from. It
could list *all* the traits that provide that method with that
How about method `foo` no found and no trait in scope provided one ?
On Thu, Dec 5, 2013 at 4:29 PM, Philippe Delrieu
philippe.delr...@free.fr wrote:
Perhaps the error message can be more explicit like trait not found for
method instead of method not found.
Le 05/12/2013 21:57, Corey
I find this message better than the current. It won't mislead me.
Le 05/12/2013 22:50, Corey Richardson a écrit :
How about method `foo` no found and no trait in scope provided one ?
On Thu, Dec 5, 2013 at 4:29 PM, Philippe Delrieu
philippe.delr...@free.fr wrote:
Perhaps the error message can
