rust/tests/ui/rfc-1445-restrict-constants-in-patterns/match-forbidden-without-eq.stderr

error: to use a constant of type `Foo` in a pattern, `Foo` must be annotated with `#[derive(PartialEq, Eq)]`
  --> $DIR/match-forbidden-without-eq.rs:11:9
   |
LL |         FOO => { }
   |         ^^^

warning: floating-point types cannot be used in patterns
  --> $DIR/match-forbidden-without-eq.rs:18:9
   |
LL |         f32::INFINITY => { }
   |         ^^^^^^^^^^^^^
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #41620 <https://github.com/rust-lang/rust/issues/41620>
   = note: `#[warn(illegal_floating_point_literal_pattern)]` on by default

error: aborting due to previous error; 1 warning emitted
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			error: to use a constant of type `Foo` in a pattern, `Foo` must be annotated with `#[derive(PartialEq, Eq)]`
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			`--> $DIR/match-forbidden-without-eq.rs:11:9`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| FOO => { }`
			`\| ^^^`

			`warning: floating-point types cannot be used in patterns`
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			`--> $DIR/match-forbidden-without-eq.rs:18:9`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| f32::INFINITY => { }`
			`\| ^^^^^^^^^^^^^`
			`\|`
			`= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!`
			`= note: for more information, see issue #41620 <https://github.com/rust-lang/rust/issues/41620>`
bless ui tests 2022-09-18 10:55:36 -05:00			= note: `#[warn(illegal_floating_point_literal_pattern)]` on by default
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
Fix double warning about illegal floating-point literal pattern 2021-07-05 10:56:43 -05:00			`error: aborting due to previous error; 1 warning emitted`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00