cannot be used on the left side of a
comparison.
If anything, the expected vector, found vector isn't particularly
helpful.
David
Regards,
Kai
2014-09-10 8:22 GMT+08:00 David Brown [1]dav...@davidb.org:
I've seen something similar recently, with this code
I've seen something similar recently, with this code:
--
fn main() {
// Fails.
assert_eq!(stuff(), []);
// Works
let tmp: 'static [uint] = [];
assert_eq!(stuff(), tmp);
}
static simple: 'static [uint] = [1, 2];
this, or do I need to allocate strings for the
copies of the individual slices?
Thanks,
David Brown
--
// life.rs
fn main() {
let info = build(String::from_str(this is a test));
println!({}, info.fields[0]);
}
struct
On Tue, Jul 08, 2014 at 03:57:27PM -0700, Brian Anderson wrote:
So we're turning it off. The previous behavior can be restored by
passing --rpath to rustc, or re-enabled for the Rust distribution
itself by passing --enable-rpath to configure.
Is the intent to have this --rpath and especially
, they are non-Send, so can't have Drop either.
Thanks,
David Brown
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
that return
cloneable values rather than references. My use cases are small types
(such as uint), so this doesn't really hurt anything.
Thanks,
David
On 2013-09-25 7:54 PM, Daniel Micay [1]danielmi...@gmail.com
wrote:
On Wed, Sep 25, 2013 at 10:36 PM, David Brown [2]dav...@davidb.org
wrote
it something else.
https://github.com/mozilla/rust/issues/6396
Carl Eastlund
On Thu, Sep 12, 2013 at 11:16 AM, David Brown dav...@davidb.org wrote:
Consider the following code
--
pub trait Inner {
fn secret(self
Somewhere between 0.5 and
rustc 0.6 (09bb07b 2012-12-24 18:29:02 -0800)
host: x86_64-unknown-linux-gnu
The program below started printing 16959 instead of 99 (16959 ==
99 0x). It seems rustc has decided to use a 16-bit integer,
even though the constant doesn't even fit.
fn
On 2012-07-12, Graydon Hoare gray...@mozilla.com wrote:
Anyway, that aside, here are some links. Please let me know what's wrong
with them (if anything obvious), which platforms they work or don't-work
on, any minor fixes to throw in last-minute: