rust/tests/ui/use-module-level-int-consts.rs

//@ run-pass

// Make sure the module level constants are still there and accessible even after
// the corresponding associated constants have been added, and later stabilized.
#![allow(deprecated, deprecated_in_future)]
use std::{u16, f32};

fn main() {
    let _ = u16::MAX;
    let _ = f32::EPSILON;
    let _ = std::f64::MANTISSA_DIGITS;
}
Add test accessing the module level int/float consts 2020-01-23 13:10:43 -06:00			`//@ run-pass`

			`// Make sure the module level constants are still there and accessible even after`
			`// the corresponding associated constants have been added, and later stabilized.`
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 18:21:40 -05:00			`#![allow(deprecated, deprecated_in_future)]`
Add test accessing the module level int/float consts 2020-01-23 13:10:43 -06:00			`use std::{u16, f32};`

			`fn main() {`
			`let _ = u16::MAX;`
			`let _ = f32::EPSILON;`
			`let _ = std::f64::MANTISSA_DIGITS;`
			`}`