rust/tests/ui/mir/mir_ascription_coercion.rs

// run-pass
// Tests that the result of type ascription has adjustments applied

#![feature(type_ascription)]

fn main() {
    let x = [1, 2, 3];
    // The RHS should coerce to &[i32]
    let _y : &[i32] = type_ascribe!(&x, &[i32; 3]);
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 07:18:55 -05:00			`// run-pass`
Handle coercion casts properly when building the MIR Coercion casts (`expr as T` where the type of `expr` can be coerced to `T`) are essentially no-ops, as the actual work is done by a coercion. Previously a check for type equality was used to avoid emitting the redundant cast in the MIR, but this failed for coercion casts of function items that had lifetime parameters. The MIR trans code doesn't handle `FnPtr -> FnPtr` casts and produced an error. Also fixes a bug with type ascription expressions not having any adjustments applied. Fixes #33295 2016-05-01 00:56:07 -05:00			`// Tests that the result of type ascription has adjustments applied`

Disable old trans access via -Z orbit, #[rustc_no_mir] or --disable-orbit. 2016-08-23 22:36:37 -05:00			`#![feature(type_ascription)]`
Handle coercion casts properly when building the MIR Coercion casts (`expr as T` where the type of `expr` can be coerced to `T`) are essentially no-ops, as the actual work is done by a coercion. Previously a check for type equality was used to avoid emitting the redundant cast in the MIR, but this failed for coercion casts of function items that had lifetime parameters. The MIR trans code doesn't handle `FnPtr -> FnPtr` casts and produced an error. Also fixes a bug with type ascription expressions not having any adjustments applied. Fixes #33295 2016-05-01 00:56:07 -05:00
			`fn main() {`
			`let x = [1, 2, 3];`
			`// The RHS should coerce to &[i32]`
Use `type_ascribe!` in many UI tests Use it in all UI tests that are about the semantics and not the syntax of type ascription. 2022-11-19 15:11:00 -06:00			`let _y : &[i32] = type_ascribe!(&x, &[i32; 3]);`
Handle coercion casts properly when building the MIR Coercion casts (`expr as T` where the type of `expr` can be coerced to `T`) are essentially no-ops, as the actual work is done by a coercion. Previously a check for type equality was used to avoid emitting the redundant cast in the MIR, but this failed for coercion casts of function items that had lifetime parameters. The MIR trans code doesn't handle `FnPtr -> FnPtr` casts and produced an error. Also fixes a bug with type ascription expressions not having any adjustments applied. Fixes #33295 2016-05-01 00:56:07 -05:00			`}`