rust/src/libcoretest/mem.rs, branch 1.0.0-beta

std: Remove #[old_orphan_check] from PartialEq

2015-03-31T20:39:14+00:00

This is a deprecated attribute that is slated for removal, and it also affects all implementors of the trait. This commit removes the attribute and fixes up implementors accordingly. The primary implementation which was lost was the ability to compare `&[T]` and `Vec` (in that order). This change also modifies the `assert_eq!` macro to not consider both directions of equality, only the one given in the left/right forms to the macro. This modification is motivated due to the fact that `&[T] == Vec` no longer compiles, causing hundreds of errors in unit tests in the standard library (and likely throughout the community as well). cc #19470 [breaking-change]

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.

Add trivial cast lints.

2015-03-24T21:03:57+00:00

This permits all coercions to be performed in casts, but adds lints to warn in those cases. Part of this patch moves cast checking to a later stage of type checking. We acquire obligations to check casts as part of type checking where we previously checked them. Once we have type checked a function or module, then we check any cast obligations which have been acquired. That means we have more type information available to check casts (this was crucial to making coercions work properly in place of some casts), but it means that casts cannot feed input into type inference. [breaking change] * Adds two new lints for trivial casts and trivial numeric casts, these are warn by default, but can cause errors if you build with warnings as errors. Previously, trivial numeric casts and casts to trait objects were allowed. * The unused casts lint has gone. * Interactions between casting and type inference have changed in subtle ways. Two ways this might manifest are: - You may need to 'direct' casts more with extra type information, for example, in some cases where `foo as _ as T` succeeded, you may now need to specify the type for `_` - Casts do not influence inference of integer types. E.g., the following used to type check: ``` let x = 42; let y = &x as *const u32; ``` Because the cast would inform inference that `x` must have type `u32`. This no longer applies and the compiler will fallback to `i32` for `x` and thus there will be a type error in the cast. The solution is to add more type information: ``` let x: u32 = 42; let y = &x as *const u32; ```

Remove integer suffixes where the types in compiled code are identical.

2015-03-05T07:08:33+00:00

Use arrays instead of vectors in tests

2015-02-24T18:15:45+00:00

Fallout: tests. As tests frequently elide things, lots of changes

2015-02-18T15:25:28+00:00

here. Some of this may have been poorly rebased, though I tried to be careful and preserve the spirit of the test.

Deprecating i/u suffixes in libcoretest

2015-02-10T22:56:31+00:00

Remove all `i` suffixes

2015-01-30T03:38:54+00:00

Generalise pointer width tests using pointer_width

2015-01-14T02:59:45+00:00

powerpc: Add backend support for powerpc

2015-01-12T05:14:30+00:00