rust/tests/ui/array-slice-vec/huge-largest-array.rs

//@ run-pass


use std::mem::size_of;

#[cfg(target_pointer_width = "32")]
pub fn main() {
    assert_eq!(size_of::<[u8; (1 << 31) - 1]>(), (1 << 31) - 1);
}

#[cfg(target_pointer_width = "64")]
pub fn main() {
    assert_eq!(size_of::<[u8; (1 << 47) - 1]>(), (1 << 47) - 1);
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
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 12:18:55 +00:00
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 20:13:15 +00:00
clearly define `int` and `uint` to fix unsoundness This fixes the gap in the language definition causing #18726 by defining a clear bound on the maximum size for libraries to enforce. Closes #18069 2014-11-07 02:30:49 +00:00			`use std::mem::size_of;`

Register new snapshots. 2015-01-16 15:01:02 +00:00			`#[cfg(target_pointer_width = "32")]`
clearly define `int` and `uint` to fix unsoundness This fixes the gap in the language definition causing #18726 by defining a clear bound on the maximum size for libraries to enforce. Closes #18069 2014-11-07 02:30:49 +00:00			`pub fn main() {`
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			`assert_eq!(size_of::<[u8; (1 << 31) - 1]>(), (1 << 31) - 1);`
clearly define `int` and `uint` to fix unsoundness This fixes the gap in the language definition causing #18726 by defining a clear bound on the maximum size for libraries to enforce. Closes #18069 2014-11-07 02:30:49 +00:00			`}`

Register new snapshots. 2015-01-16 15:01:02 +00:00			`#[cfg(target_pointer_width = "64")]`
clearly define `int` and `uint` to fix unsoundness This fixes the gap in the language definition causing #18726 by defining a clear bound on the maximum size for libraries to enforce. Closes #18069 2014-11-07 02:30:49 +00:00			`pub fn main() {`
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			`assert_eq!(size_of::<[u8; (1 << 47) - 1]>(), (1 << 47) - 1);`
clearly define `int` and `uint` to fix unsoundness This fixes the gap in the language definition causing #18726 by defining a clear bound on the maximum size for libraries to enforce. Closes #18069 2014-11-07 02:30:49 +00:00			`}`