2018-09-04 05:26:21 -05:00
error[E0080]: it is undefined behavior to use this value
2021-06-03 02:31:27 -05:00
--> $DIR/ref_to_int_match.rs:25:1
2018-05-24 04:03:33 -05:00
|
2019-03-09 06:03:44 -06:00
LL | const BAR: Int = unsafe { Foo { r: &42 }.f };
2022-05-19 13:16:25 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ type validation failed: encountered pointer to alloc3, but expected plain (non-pointer) bytes
2018-09-04 05:26:21 -05:00
|
2019-09-01 12:09:59 -05:00
= note: The rules on what exactly is undefined behavior aren't clear, so this check might be overzealous. Please open an issue on the rustc repository if you believe it should not be considered undefined behavior.
2021-02-01 06:02:31 -06:00
= note: the raw bytes of the constant (size: 8, align: 8) {
2021-07-12 17:21:35 -05:00
╾───────alloc3────────╼ │ ╾──────╼
2021-02-01 06:02:31 -06:00
}
2018-09-04 05:26:21 -05:00
error: could not evaluate constant pattern
2021-06-03 02:31:27 -05:00
--> $DIR/ref_to_int_match.rs:7:14
2018-09-04 05:26:21 -05:00
|
2019-03-09 06:03:44 -06:00
LL | 10..=BAR => {},
2018-09-04 05:26:21 -05:00
| ^^^
2018-05-24 04:03:33 -05:00
2020-01-08 11:02:10 -06:00
error: could not evaluate constant pattern
2021-06-03 02:31:27 -05:00
--> $DIR/ref_to_int_match.rs:7:14
2020-01-08 11:02:10 -06:00
|
LL | 10..=BAR => {},
| ^^^
error: aborting due to 3 previous errors
2018-05-24 04:03:33 -05:00
2018-09-04 05:26:21 -05:00
For more information about this error, try `rustc --explain E0080`.