rust/src/test/debuginfo/c-style-enum.rs, branch 1.3.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.3.02015-04-01T15:22:39+00:00Fallout in tests2015-04-01T15:22:39+00:00Niko Matsakisniko@alum.mit.edu2015-03-30T13:38:27+00:00urn:sha1:890ed5c46847fa544278c18fd46c1bdfe2809c09Fix fallout of removing quotes in crate names2015-03-27T18:43:40+00:00Alex Crichtonalex@alexcrichton.com2015-03-27T17:22:44+00:00urn:sha1:e77db16afbe9a7180242112456c7fded48f21b6dIgnore some tests on aarch642015-03-25T09:17:33+00:00Sae-bom Kimsae-bom.kim@samsung.com2015-03-25T09:17:33+00:00urn:sha1:c66a2b7393afe332ee8bf6aba985e4fdd253cf54Enable test/debuginfo on android2015-02-10T06:48:07+00:00Eunji Jeongeun-ji.jeong@samsung.com2015-01-30T06:21:56+00:00urn:sha1:b1af8648a7697172fc10c50e9e79bed6689d4f5dUse `derive` rather than `deriving` in tests2015-01-02T10:05:22+00:00Nick Cameronncameron@mozilla.com2014-12-31T04:32:49+00:00urn:sha1:30e149231c627e61524d1b5bd6357886befae9e6debuginfo: Add a rust-gdb shell script that will start GDB with Rust pretty printers enabled.2014-12-30T16:26:13+00:00Michael Woeristermichaelwoerister@posteo2014-12-03T22:48:18+00:00urn:sha1:91a0e18866d143c045e9e29377a6e918011c0b63librustc: Make `Copy` opt-in.2014-12-08T18:47:44+00:00Niko Matsakisniko@alum.mit.edu2014-12-06T01:01:33+00:00urn:sha1:096a28607fb80c91e6e2ca64d9ef44c4e550e96c
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]
Switch to purely namespaced enums2014-11-17T15:35:51+00:00Steven Facklersfackler@gmail.com2014-11-06T08:05:53+00:00urn:sha1:3dcd2157403163789aaf21a9ab3c4d30a7c6494d
This breaks code that referred to variant names in the same namespace as
their enum. Reexport the variants in the old location or alter code to
refer to the new locations:
```
pub enum Foo {
A,
B
}
fn main() {
let a = A;
}
```
=>
```
pub use self::Foo::{A, B};
pub enum Foo {
A,
B
}
fn main() {
let a = A;
}
```
or
```
pub enum Foo {
A,
B
}
fn main() {
let a = Foo::A;
}
```
[breaking-change]
debuginfo: Enable some GDB tests on Windows.2014-10-31T17:49:59+00:00Michael Woeristermichaelwoerister@posteo2014-10-30T06:08:27+00:00urn:sha1:e06c3382739a01725b10b893df613413f2923e8adebuginfo: Make GDB tests use line breakpoints like done in LLDB tests.2014-10-31T17:49:59+00:00Michael Woeristermichaelwoerister@posteo2014-10-29T06:13:29+00:00urn:sha1:54a5a2b36591d6aad7e94cf6740988202f1654aa
On some Windows versions of GDB this is more stable than setting breakpoints via function names.