rust/tests/ui/issues/issue-14845.rs

struct X {
    a: [u8; 1]
}

fn main() {
    let x = X { a: [0] };
    let _f = &x.a as *mut u8; //~ ERROR casting

    let local: [u8; 1] = [0];
    let _v = &local as *mut u8; //~ ERROR casting
}
librustc: Take in account mutability when casting array to raw ptr. 2014-06-12 22:58:37 +00:00			`struct X {`
Allow use of `[_ ; n]` syntax for fixed length and repeating arrays. This does NOT break any existing programs because the `[_, ..n]` syntax is also supported. 2014-12-20 02:20:51 +00:00			`a: [u8; 1]`
librustc: Take in account mutability when casting array to raw ptr. 2014-06-12 22:58:37 +00:00			`}`

			`fn main() {`
			`let x = X { a: [0] };`
Improve typeck diagnostic messages Mostly by splitting error messages into proper pairs of errors and helps 2015-07-27 00:31:38 +00:00			`let _f = &x.a as *mut u8; //~ ERROR casting`
Rolling up PRs in the queue Closes #14797 (librustc: Fix the issue with labels shadowing variable names by making) Closes #14823 (Improve error messages for io::fs) Closes #14827 (libsyntax: Allow `+` to separate trait bounds from objects.) Closes #14834 (configure: Don't sync unused submodules) Closes #14838 (Remove typo on collections::treemap::UnionItems) Closes #14839 (Fix the unused struct field lint for struct variants) Closes #14840 (Clarify `Any` docs) Closes #14846 (rustc: [T, ..N] and [T, ..N+1] are not the same) Closes #14847 (Audit usage of NativeMutex) Closes #14850 (remove unnecessary PaX detection) Closes #14856 (librustc: Take in account mutability when casting array to raw ptr.) Closes #14859 (librustc: Forbid `transmute` from being called on types whose size is) Closes #14860 (Fix `quote_pat!` & parse outer attributes in `quote_item!`) 2014-06-13 04:34:32 +00:00
Add trivial cast lints. 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; ``` 2015-03-20 04:15:27 +00:00			`let local: [u8; 1] = [0];`
Improve typeck diagnostic messages Mostly by splitting error messages into proper pairs of errors and helps 2015-07-27 00:31:38 +00:00			`let _v = &local as *mut u8; //~ ERROR casting`
librustc: Take in account mutability when casting array to raw ptr. 2014-06-12 22:58:37 +00:00			`}`