rust/tests/ui/consts/const-err-multi.rs

pub const A: i8 = -i8::MIN;
//~^ NOTE failed here
//~| ERROR attempt to negate `i8::MIN`, which would overflow
pub const B: i8 = A;
//~^ NOTE erroneous constant
pub const C: u8 = A as u8;
//~^ NOTE erroneous constant
pub const D: i8 = 50 - A;
//~^ NOTE erroneous constant

fn main() {
    let _ = (A, B, C, D);
}
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			`pub const A: i8 = -i8::MIN;`
const-eval error: always say in which item the error occurred also adjust the wording a little so that we don't say "the error occurred here" for two different spans 2025-06-07 11:32:09 +02:00			`//~^ NOTE failed here`
Use the informative error as the main const eval error message 2025-05-28 10:29:08 +00:00			//~\| ERROR attempt to negate `i8::MIN`, which would overflow
Report const eval error inside the query 2018-08-26 15:19:34 +02:00			`pub const B: i8 = A;`
const-eval error: always say in which item the error occurred also adjust the wording a little so that we don't say "the error occurred here" for two different spans 2025-06-07 11:32:09 +02:00			`//~^ NOTE erroneous constant`
don't report errors in constants at every use site 2016-04-11 10:41:48 +02:00			`pub const C: u8 = A as u8;`
const-eval error: always say in which item the error occurred also adjust the wording a little so that we don't say "the error occurred here" for two different spans 2025-06-07 11:32:09 +02:00			`//~^ NOTE erroneous constant`
don't report errors in constants at every use site 2016-04-11 10:41:48 +02:00			`pub const D: i8 = 50 - A;`
const-eval error: always say in which item the error occurred also adjust the wording a little so that we don't say "the error occurred here" for two different spans 2025-06-07 11:32:09 +02:00			`//~^ NOTE erroneous constant`
don't report errors in constants at every use site 2016-04-11 10:41:48 +02:00
			`fn main() {`
Update tests 2018-01-29 20:47:09 +01:00			`let _ = (A, B, C, D);`
don't report errors in constants at every use site 2016-04-11 10:41:48 +02:00			`}`