rust/tests/ui/limits/issue-55878.rs

//@ build-fail
//@ normalize-stderr-64bit: "18446744073709551615" -> "SIZE"
//@ normalize-stderr-32bit: "4294967295" -> "SIZE"

//@ error-pattern: are too big for the current architecture
fn main() {
    println!("Size: {}", std::mem::size_of::<[u8; u64::MAX as usize]>());
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ build-fail`
Always use a colon in `//@ normalize-*:` headers 2024-06-21 15:15:36 +10:00			`//@ normalize-stderr-64bit: "18446744073709551615" -> "SIZE"`
			`//@ normalize-stderr-32bit: "4294967295" -> "SIZE"`
fix tests 2019-08-04 21:18:05 -07:00
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ error-pattern: are too big for the current architecture`
Always error on `SizeOverflow` during mir evaluation 2019-07-30 17:46:46 -07:00			`fn main() {`
Update tests to remove old numeric constants Part of #68490. Care has been taken to leave the old consts where appropriate, for testing backcompat regressions, module shadowing, etc. The intrinsics docs were accidentally referring to some methods on f64 as std::f64, which I changed due to being contrary with how we normally disambiguate the shadow module from the primitive. In one other place I changed std::u8 to std::ops since it was just testing path handling in macros. For places which have legitimate uses of the old consts, deprecated attributes have been optimistically inserted. Although currently unnecessary, they exist to emphasize to any future deprecation effort the necessity of these specific symbols and prevent them from being accidentally removed. 2020-10-24 19:21:40 -04:00			`println!("Size: {}", std::mem::size_of::<[u8; u64::MAX as usize]>());`
Always error on `SizeOverflow` during mir evaluation 2019-07-30 17:46:46 -07:00			`}`