rust/src/test/debuginfo/method-on-trait.rs, branch 1.3.0

Fallout in tests

2015-04-01T15:22:39+00:00

Mass rename uint/int to usize/isize

2015-03-26T19:10:22+00:00

Now that support has been removed, all lingering use cases are renamed.

Strip all leading/trailing newlines

2015-03-15T16:08:21+00:00

Add `: Box<_>` or `::Box<_>` type annotations to various places.

2015-03-03T19:29:01+00:00

This is the kind of change that one is expected to need to make to accommodate overloaded-`box`. ---- Note that this is not *all* of the changes necessary to accommodate Issue 22181. It is merely the subset of those cases where there was already a let-binding in place that made it easy to add the necesasry type ascription. (For unnamed intermediate `Box` values, one must go down a different route; `Box::new` is the option that maximizes portability, but has potential inefficiency depending on whether the call is inlined.) ---- There is one place worth note, `run-pass/coerce-match.rs`, where I used an ugly form of `Box<_>` type ascription where I would have preferred to use `Box::new` to accommodate overloaded-`box`. I deliberately did not use `Box::new` here, because that is already done in coerce-match-calls.rs. ---- Precursor for overloaded-`box` and placement-`in`; see Issue 22181.

Enable test/debuginfo on android

2015-02-10T06:48:07+00:00

cleanup: s/impl Copy/#[derive(Copy)]/g

2015-01-25T16:20:38+00:00

Test fixes and rebase conflicts

2015-01-08T03:27:27+00:00

debuginfo: Add a rust-gdb shell script that will start GDB with Rust pretty printers enabled.

2014-12-30T16:26:13+00:00

librustc: Make `Copy` opt-in.

2014-12-08T18:47:44+00:00

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]

debuginfo: Make GDB tests use line breakpoints like done in LLDB tests.

2014-10-31T17:49:59+00:00

On some Windows versions of GDB this is more stable than setting breakpoints via function names.