granite-rust/tests/ui/transmute-non-immediate-to-immediate.rs

//@ run-pass
// Issue #7988
// Transmuting non-immediate type to immediate type

//@ pretty-expanded FIXME #23616

pub fn main() {
    unsafe {
        ::std::mem::transmute::<[isize; 1],isize>([1])
    };
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
Fix a crash when transmuting non-immediate to immediate types The code to build the transmute intrinsic currently makes the invalid assumption that if the in-type is non-immediate, the out-type is non-immediate as well. But this is wrong, for example when transmuting [int, ..1] to int. So we need to handle this fourth case as well. Fixes #7988 2013-07-23 09:37:00 +02:00			`// Issue #7988`
			`// Transmuting non-immediate type to immediate type`

[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ pretty-expanded FIXME #23616`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 13:13:15 -07:00
Fix run-pass tests to have 'pub fn main' This is required by the check-fast target because each test is slurped up into a submodule. 2013-09-25 00:43:37 -07:00			`pub fn main() {`
Fix a crash when transmuting non-immediate to immediate types The code to build the transmute intrinsic currently makes the invalid assumption that if the in-type is non-immediate, the out-type is non-immediate as well. But this is wrong, for example when transmuting [int, ..1] to int. So we need to handle this fourth case as well. Fixes #7988 2013-07-23 09:37:00 +02:00			`unsafe {`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`::std::mem::transmute::<[isize; 1],isize>([1])`
Fix a crash when transmuting non-immediate to immediate types The code to build the transmute intrinsic currently makes the invalid assumption that if the in-type is non-immediate, the out-type is non-immediate as well. But this is wrong, for example when transmuting [int, ..1] to int. So we need to handle this fourth case as well. Fixes #7988 2013-07-23 09:37:00 +02:00			`};`
			`}`