Files
rust/tests/crashes
bors 42b384ec0d Auto merge of #147055 - beepster4096:subtype_is_not_a_projection, r=lcnr
Turn ProjectionElem::Subtype into CastKind::Subtype

I noticed that drop elaboration can't, in general, handle `ProjectionElem::SubType`. It creates a disjoint move path that overlaps with other move paths. (`Subslice` does too, and I'm working on a different PR to make that special case less fragile.) If its skipped and treated as the same move path as its parent then `MovePath.place` has multiple possible projections. (It would probably make sense to remove all `Subtype` projections for the canonical place but it doesn't make sense to have this special case for a problem that doesn't actually occur in real MIR.)

The only reason this doesn't break is that `Subtype` is always the sole projection of the local its applied to. For the same reason, it works fine as a `CastKind` so I figured that makes more sense than documenting and validating this hidden invariant.

cc rust-lang/rust#112651, rust-lang/rust#133258

r? Icnr (bc you've been the main person dealing with `Subtype` it looks like)
2025-10-02 01:54:48 +00:00
..
2025-05-21 20:20:19 +01:00
2025-09-29 11:04:50 +10:00
2024-04-26 17:20:16 +02:00
2024-04-19 23:09:37 +02:00
2024-04-19 23:09:37 +02:00
2025-01-25 23:40:35 +01:00
2024-04-18 18:55:20 +02:00
2025-06-11 15:30:15 +01:00
2024-04-18 18:55:20 +02: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
2025-09-26 15:37:19 -07:00
2024-04-18 18:55:20 +02:00
2024-04-18 06:13:47 +02:00
2024-05-29 17:06:54 +01:00
2024-04-18 18:55:20 +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-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
2025-09-29 11:04:50 +10: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-29 09:33:28 +02:00
2024-06-29 09:33:28 +02:00
2025-05-01 20:05:07 +01:00
2024-08-19 00:38:28 +02:00
2024-08-30 12:38:22 +02:00
2024-08-30 12:38:22 +02:00
2025-06-25 00:52:10 -07: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-12-15 17:27:52 +01:00
2024-10-09 15:34:45 +02:00
2024-10-09 15:34:45 +02:00
2025-09-29 11:04:50 +10: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-12 11:29:38 +02:00
2024-10-20 10:05:39 +02:00
2024-10-20 10:05:39 +02:00
2024-11-02 23:44:12 +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
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-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-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-01 17:04:37 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02:00
2025-05-18 17:25:34 +02: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!