dianne 36ff87e90e EUV: fix place of deref pattern's interior's scrutinee
The place previously used here was that of the temporary holding the
reference returned by `Deref::deref` or `DerefMut::deref_mut`. However,
since the inner pattern of `deref!(inner)` expects the deref-target type
itself, this would ICE when that type was inspected (e.g. by the EUV
case for slice patterns). This adds a deref projection to fix that.

Since current in-tree consumers of EUV (upvar inference and clippy)
don't care about Rvalues, the place could be simplified to
`self.cat_rvalue(pat.hir_id, self.pat_ty_adjusted(subpat)?)` to save
some cycles. I personally find EUV to be a bit fragile, so I've opted
for pedantic correctness. Maybe a `HACK` comment would suffice though?
2025-03-13 01:01:26 -07:00
..
2024-12-12 22:09:39 +01:00
2024-04-26 17:20:16 +02:00
2024-04-18 18:55:20 +02:00
2024-04-19 23:09:37 +02:00
2024-04-19 23:09:37 +02:00
2024-04-18 18:55:20 +02:00
2025-01-25 23:40:35 +01:00
2024-04-18 18:55:20 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 18:55:20 +02:00
2024-04-19 23:09:37 +02:00
2024-12-08 14:17:25 +01:00
2024-12-08 14:17:25 +01:00
2024-04-19 23:09:37 +02:00
2024-04-18 18:55:20 +02:00
2024-12-08 14:17:25 +01:00
2024-12-08 14:17:25 +01:00
2024-04-18 18:55:20 +02:00
2024-12-08 14:17:25 +01:00
2024-04-18 18:55:20 +02:00
2024-04-18 06:13:47 +02:00
2024-12-08 14:17:25 +01:00
2024-04-18 18:55:20 +02:00
2024-05-29 17:06:54 +01:00
2024-04-18 18:55:20 +02:00
2024-04-18 18:55:20 +02:00
2024-04-18 06:13:47 +02:00
2024-09-01 22:28:23 +02:00
2024-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02:00
2024-12-08 14:17:25 +01:00
2024-04-18 06:13:47 +02:00
2024-04-21 21:04:32 +02:00
2024-04-26 17:20:16 +02:00
2024-04-26 17:20:16 +02:00
2024-11-22 11:12:15 -08:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-06-09 10:16:12 +02:00
2024-11-02 23:44:12 +01:00
2024-06-16 20:38:08 +02:00
2024-06-29 09:33:28 +02:00
2024-06-29 09:33:28 +02:00
2024-07-04 23:44:10 +02:00
2024-09-01 22:28:23 +02:00
2024-07-21 17:50:57 +02:00
2024-08-15 22:44:16 +02:00
2024-08-19 00:38:28 +02:00
2024-09-01 22:28:23 +02:00
2024-08-30 12:38:22 +02:00
2024-08-30 12:38:22 +02:00
2024-09-15 21:18:41 +02:00
2024-09-15 21:18:41 +02:00
2024-12-08 14:17:25 +01:00
2024-09-18 00:10:25 +02:00
2024-09-29 11:58:09 +02:00
2024-09-29 11:58:09 +02:00
2024-12-15 17:27:52 +01:00
2024-10-09 15:34:45 +02:00
2024-10-09 15:34:45 +02:00
2024-10-09 15:34:45 +02:00
2024-10-09 15:34:45 +02:00
2024-10-09 15:34:45 +02:00
2024-10-09 15:34:45 +02:00
2024-10-09 15:34:45 +02:00
2024-12-08 13:09:46 +01:00
2024-10-12 11:29:38 +02:00
2024-10-20 10:05:39 +02:00
2024-10-20 10:05:39 +02:00
2024-10-20 10:05:39 +02:00
2024-12-15 17:27:52 +01:00
2024-11-02 23:44:12 +01:00
2024-11-06 22:10:23 +01:00
2024-11-06 22:10:23 +01:00
2024-11-06 22:10:23 +01:00
2024-12-12 22:09:39 +01:00
2025-01-25 23:40:35 +01:00
2024-12-12 22:09:39 +01:00
2024-12-12 22:09:39 +01:00
2024-12-12 22:09:39 +01:00
2024-12-12 22:09:39 +01:00
2024-12-12 22:09:39 +01:00
2024-12-15 17:27:52 +01:00
2024-12-12 22:55:31 +01:00
2024-12-12 22:55:31 +01:00
2024-12-12 22:55:31 +01:00
2024-12-12 22:55:31 +01:00
2024-12-12 22:55:31 +01:00
2024-12-15 17:27:52 +01:00
2024-12-12 22:55:31 +01:00
2024-12-15 17:27:52 +01:00
2024-12-15 17:27:52 +01:00
2025-01-04 14:38:06 +01:00
2025-01-04 14:38:06 +01:00
2025-01-04 14:38:06 +01:00
2025-01-04 14:38:06 +01:00
2025-01-04 14:38:06 +01:00
2025-01-12 10:11:29 +01:00
2025-02-09 10:40:18 +01:00
2025-02-09 10:40:18 +01:00
2025-02-09 10:40:18 +01:00
2025-02-09 10:40:18 +01:00
2025-02-09 10:40:18 +01:00
2025-02-09 10:40:18 +01:00
2025-02-09 10:40:18 +01:00
2025-02-09 10:40:18 +01:00
2025-02-09 10:40:18 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00
2025-03-08 20:13:07 +01:00

This is serves as a collection of crashes so that accidental ICE fixes are tracked. This was formally done at https://github.com/rust-lang/glacier but doing it inside the rustc testsuite is more convenient.

It is imperative that a test in the suite causes an internal compiler error/panic or makes rustc crash in some other way. A test will "pass" if rustc exits with something other than 1 or 0.

When adding crashes from https://github.com/rust-lang/rust/issues, the issue number should be noted in the file name (12345.rs should suffice) and also inside the file via //@ known-bug #4321 if possible.

If you happen to fix one of the crashes, please move it to a fitting subdirectory in tests/ui and give it a meaningful name. Also please add a doc comment at the top of the file explaining why this test exists. :) Adding Fixes #NNNNN Fixes #MMMMM to the description of your pull request will ensure the corresponding tickets will be closed automatically upon merge. The ticket ids can be found in the file name or the known-bug annotation inside the testfile.

Please do not re-report any crashes that you find here!