bors f4966590d8 Auto merge of #131045 - compiler-errors:remove-unnamed_fields, r=wesleywiser
Retire the `unnamed_fields` feature for now

`#![feature(unnamed_fields)]` was implemented in part in #115131 and #115367, however work on that feature has (afaict) stalled and in the mean time there have been some concerns raised (e.g.[^1][^2]) about whether `unnamed_fields` is worthwhile to have in the language, especially in its current desugaring. Because it represents a compiler implementation burden including a new kind of anonymous ADT and additional complication to field selection, and is quite prone to bugs today, I'm choosing to remove the feature.

However, since I'm not one to really write a bunch of words, I'm specifically *not* going to de-RFC this feature. This PR essentially *rolls back* the state of this feature to "RFC accepted but not yet implemented"; however if anyone wants to formally unapprove the RFC from the t-lang side, then please be my guest. I'm just not totally willing to summarize the various language-facing reasons for why this feature is or is not worthwhile, since I'm coming from the compiler side mostly.

Fixes #117942
Fixes #121161
Fixes #121263
Fixes #121299
Fixes #121722
Fixes #121799
Fixes #126969
Fixes #131041

Tracking:
* https://github.com/rust-lang/rust/issues/49804

[^1]: https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/Unnamed.20struct.2Funion.20fields
[^2]: https://github.com/rust-lang/rust/issues/49804#issuecomment-1972619108
2024-10-11 13:11:13 +00: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-19 23:09:37 +02:00
2024-04-18 18:55:20 +02: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-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-04-19 23:09:37 +02:00
2024-04-18 18:55:20 +02:00
2024-04-18 18:55:20 +02:00
2024-06-30 17:08:45 +00:00
2024-09-18 00:10:25 +02: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-04-18 18:55:20 +02: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-05-29 17:06:54 +01: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-04-18 06:13:47 +02:00
2024-04-18 06:13:47 +02: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-04-26 17:20:16 +02:00
2024-10-06 18:12:25 +02:00
2024-05-18 23:56:57 +02:00
2024-06-28 14:20:43 -04: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-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-16 20:38:08 +02:00
2024-06-16 20:38:08 +02: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-06-29 09:33:28 +02:00
2024-06-29 09:33:28 +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-07-04 23:44:10 +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-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-07-21 17:50:57 +02:00
2024-09-18 00:10:25 +02:00
2024-07-21 17:50:57 +02:00
2024-08-04 21:25:49 +02:00
2024-09-18 00:10:25 +02:00
2024-08-04 21:25:49 +02:00
2024-09-18 00:10:25 +02:00
2024-08-04 21:25:49 +02:00
2024-08-15 22:44:16 +02:00
2024-08-15 22:44:16 +02:00
2024-08-15 22:44:16 +02:00
2024-08-15 22:44:16 +02:00
2024-08-15 22:44:16 +02:00
2024-08-15 22:44:16 +02:00
2024-08-19 00:38:28 +02:00
2024-08-19 00:38:28 +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-08-30 12:38:22 +02:00
2024-09-15 21:18:41 +02:00
2024-09-15 21:18:41 +02:00
2024-09-18 00:10:25 +02: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-09-29 11:58:09 +02:00
2024-09-29 11:58:09 +02:00
2024-09-29 11:58:09 +02:00
2024-10-09 15:34:45 +02:00
2024-10-09 15:34:45 +02:00
2024-09-29 11:58:09 +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-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-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

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 perhaps also inside the file via //@ known-bug #4321

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.