rust/tests/ui/rfcs/rfc-1445-restrict-constants-in-patterns/issue-63479-match-fnptr.stderr

error: function pointers and raw pointers not derived from integers in patterns behave unpredictably and should not be relied upon
  --> $DIR/issue-63479-match-fnptr.rs:32:7
   |
LL | const TEST: Fn = my_fn;
   | -------------- constant defined here
...
LL |     B(TEST) => println!("matched"),
   |       ^^^^ can't be used in patterns
   |
   = note: see https://github.com/rust-lang/rust/issues/70861 for details

error: function pointers and raw pointers not derived from integers in patterns behave unpredictably and should not be relied upon
  --> $DIR/issue-63479-match-fnptr.rs:37:5
   |
LL | const TEST2: (Fn, u8) = (TEST, 0);
   | --------------------- constant defined here
...
LL |     TEST2 => println!("matched"),
   |     ^^^^^ can't be used in patterns
   |
   = note: see https://github.com/rust-lang/rust/issues/70861 for details

error: aborting due to 2 previous errors
Tweak ptr in pattern error Conform to error style guide. 2024-11-20 03:00:58 +00:00			`error: function pointers and raw pointers not derived from integers in patterns behave unpredictably and should not be relied upon`
turn pointer_structural_match into a hard error 2024-05-03 15:49:10 +02:00			`--> $DIR/issue-63479-match-fnptr.rs:32:7`
Lint on function pointers used in patterns 2020-09-20 17:11:00 +02:00			`\|`
On `const` pattern errors, point at the `const` item definition Centralize emitting an error in `const_to_pat` so that all errors from that evaluating a `const` in a pattern can add addditional information. With this, now point at the `const` item's definition: ``` error[E0158]: constant pattern depends on a generic parameter --> $DIR/associated-const-type-parameter-pattern.rs:20:9 \| LL \| pub trait Foo { \| ------------- LL \| const X: EFoo; \| ------------- constant defined here ... LL \| A::X => println!("A::X"), \| ^^^^ ``` 2024-11-20 02:15:21 +00:00			`LL \| const TEST: Fn = my_fn;`
			`\| -------------- constant defined here`
			`...`
Lint on function pointers used in patterns 2020-09-20 17:11:00 +02:00			`LL \| B(TEST) => println!("matched"),`
Tweak ptr in pattern error Conform to error style guide. 2024-11-20 03:00:58 +00:00			`\| ^^^^ can't be used in patterns`
			`\|`
			`= note: see https://github.com/rust-lang/rust/issues/70861 for details`
Lint on function pointers used in patterns 2020-09-20 17:11:00 +02:00
Tweak ptr in pattern error Conform to error style guide. 2024-11-20 03:00:58 +00:00			`error: function pointers and raw pointers not derived from integers in patterns behave unpredictably and should not be relied upon`
turn pointer_structural_match into a hard error 2024-05-03 15:49:10 +02:00			`--> $DIR/issue-63479-match-fnptr.rs:37:5`
also lint against fn ptr and raw ptr nested inside the const 2023-10-20 08:35:36 +02:00			`\|`
On `const` pattern errors, point at the `const` item definition Centralize emitting an error in `const_to_pat` so that all errors from that evaluating a `const` in a pattern can add addditional information. With this, now point at the `const` item's definition: ``` error[E0158]: constant pattern depends on a generic parameter --> $DIR/associated-const-type-parameter-pattern.rs:20:9 \| LL \| pub trait Foo { \| ------------- LL \| const X: EFoo; \| ------------- constant defined here ... LL \| A::X => println!("A::X"), \| ^^^^ ``` 2024-11-20 02:15:21 +00:00			`LL \| const TEST2: (Fn, u8) = (TEST, 0);`
			`\| --------------------- constant defined here`
			`...`
also lint against fn ptr and raw ptr nested inside the const 2023-10-20 08:35:36 +02:00			`LL \| TEST2 => println!("matched"),`
Tweak ptr in pattern error Conform to error style guide. 2024-11-20 03:00:58 +00:00			`\| ^^^^^ can't be used in patterns`
			`\|`
			`= note: see https://github.com/rust-lang/rust/issues/70861 for details`
Lint on function pointers used in patterns 2020-09-20 17:11:00 +02:00
turn pointer_structural_match into a hard error 2024-05-03 15:49:10 +02:00			`error: aborting due to 2 previous errors`
show indirect_structural_match and pointer_structural_match in future compat reports 2024-01-27 13:52:06 +01:00