os-rust/tests/ui/range/range-1.rs

// Test range syntax - type errors.

pub fn main() {
    // Mixed types.
    let _ = 0u32..10i32;
    //~^ ERROR mismatched types

    // Bool => does not implement iterator.
    for i in false..true {}
    //~^ ERROR `bool: Step` is not satisfied

    // Unsized type.
    let arr: &[_] = &[1, 2, 3];
    let range = *arr..;
    //~^ ERROR the size for values of type
}
Tests 2014-12-15 14:23:00 +13:00			`// Test range syntax - type errors.`

			`pub fn main() {`
			`// Mixed types.`
Kill more `isize`s 2015-01-31 17:23:42 +01:00			`let _ = 0u32..10i32;`
adjust range tests Since the desugaring removed special handling for ranges, the error message changed and so I had to adjust `range-1`. Turns out there was a bug where borrowck was too restrictive in some rare cases of constructing ranges from literals. The `range-2` test enshrined this bug -- now it's adjusted to test a case that's actually wrong. 2016-01-13 01:29:39 -05:00			`//~^ ERROR mismatched types`
Tests 2014-12-15 14:23:00 +13:00
Stabilize std::num This commit stabilizes the `std::num` module: * The `Int` and `Float` traits are deprecated in favor of (1) the newly-added inherent methods and (2) the generic traits available in rust-lang/num. * The `Zero` and `One` traits are reintroduced in `std::num`, which together with various other traits allow you to recover the most common forms of generic programming. * The `FromStrRadix` trait, and associated free function, is deprecated in favor of inherent implementations. * A wide range of methods and constants for both integers and floating point numbers are now `#[stable]`, having been adjusted for integer guidelines. * `is_positive` and `is_negative` are renamed to `is_sign_positive` and `is_sign_negative`, in order to address #22985 * The `Wrapping` type is moved to `std::num` and stabilized; `WrappingOps` is deprecated in favor of inherent methods on the integer types, and direct implementation of operations on `Wrapping<X>` for each concrete integer type `X`. Closes #22985 Closes #21069 [breaking-change] 2015-03-19 23:42:18 -07:00			`// Bool => does not implement iterator.`
			`for i in false..true {}`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			//~^ ERROR `bool: Step` is not satisfied
Tests 2014-12-15 14:23:00 +13:00
			`// Unsized type.`
Remove integer suffixes where the types in compiled code are identical. 2015-03-03 10:42:26 +02:00			`let arr: &[_] = &[1, 2, 3];`
remove unnecessary parentheses from range notation 2015-01-19 11:07:13 -05:00			`let range = *arr..;`
Fix typo in error message E0277 2018-07-10 23:10:13 +02:00			`//~^ ERROR the size for values of type`
Tests 2014-12-15 14:23:00 +13:00			`}`