2024-02-17 04:02:50 +08:00
|
|
|
//@ run-pass
|
2013-09-02 21:33:17 +08:00
|
|
|
/*
|
|
|
|
|
# Corrupted initialization in the static struct
|
|
|
|
|
|
|
|
|
|
...should print &[1, 2, 3] but instead prints something like
|
|
|
|
|
&[4492532864, 24]. It is pretty evident that the compiler messed up
|
2015-03-26 08:06:52 +08:00
|
|
|
with the representation of [isize; n] and [isize] somehow, or at least
|
2013-09-02 21:33:17 +08:00
|
|
|
failed to typecheck correctly.
|
|
|
|
|
*/
|
|
|
|
|
|
2015-03-30 21:38:27 +08:00
|
|
|
#[derive(Copy, Clone)]
|
2015-03-26 08:06:52 +08:00
|
|
|
struct X { vec: &'static [isize] }
|
librustc: Make `Copy` opt-in.
This change makes the compiler no longer infer whether types (structures
and enumerations) implement the `Copy` trait (and thus are implicitly
copyable). Rather, you must implement `Copy` yourself via `impl Copy for
MyType {}`.
A new warning has been added, `missing_copy_implementations`, to warn
you if a non-generic public type has been added that could have
implemented `Copy` but didn't.
For convenience, you may *temporarily* opt out of this behavior by using
`#![feature(opt_out_copy)]`. Note though that this feature gate will never be
accepted and will be removed by the time that 1.0 is released, so you should
transition your code away from using it.
This breaks code like:
#[deriving(Show)]
struct Point2D {
x: int,
y: int,
}
fn main() {
let mypoint = Point2D {
x: 1,
y: 1,
};
let otherpoint = mypoint;
println!("{}{}", mypoint, otherpoint);
}
Change this code to:
#[deriving(Show)]
struct Point2D {
x: int,
y: int,
}
impl Copy for Point2D {}
fn main() {
let mypoint = Point2D {
x: 1,
y: 1,
};
let otherpoint = mypoint;
println!("{}{}", mypoint, otherpoint);
}
This is the backwards-incompatible part of #13231.
Part of RFC #3.
[breaking-change]
2014-12-06 09:01:33 +08:00
|
|
|
|
2013-09-02 21:33:17 +08:00
|
|
|
static V: &'static [X] = &[X { vec: &[1, 2, 3] }];
|
librustc: Make `Copy` opt-in.
This change makes the compiler no longer infer whether types (structures
and enumerations) implement the `Copy` trait (and thus are implicitly
copyable). Rather, you must implement `Copy` yourself via `impl Copy for
MyType {}`.
A new warning has been added, `missing_copy_implementations`, to warn
you if a non-generic public type has been added that could have
implemented `Copy` but didn't.
For convenience, you may *temporarily* opt out of this behavior by using
`#![feature(opt_out_copy)]`. Note though that this feature gate will never be
accepted and will be removed by the time that 1.0 is released, so you should
transition your code away from using it.
This breaks code like:
#[deriving(Show)]
struct Point2D {
x: int,
y: int,
}
fn main() {
let mypoint = Point2D {
x: 1,
y: 1,
};
let otherpoint = mypoint;
println!("{}{}", mypoint, otherpoint);
}
Change this code to:
#[deriving(Show)]
struct Point2D {
x: int,
y: int,
}
impl Copy for Point2D {}
fn main() {
let mypoint = Point2D {
x: 1,
y: 1,
};
let otherpoint = mypoint;
println!("{}{}", mypoint, otherpoint);
}
This is the backwards-incompatible part of #13231.
Part of RFC #3.
[breaking-change]
2014-12-06 09:01:33 +08:00
|
|
|
|
2013-09-25 15:43:37 +08:00
|
|
|
pub fn main() {
|
2015-02-01 01:20:46 +08:00
|
|
|
for &v in V {
|
2015-01-08 06:58:31 +08:00
|
|
|
println!("{:?}", v.vec);
|
2013-09-02 21:33:17 +08:00
|
|
|
}
|
|
|
|
|
}
|