3 Commits

Author	SHA1	Message	Date
Jordan Rose	7c689c322e	Prefer @unknown default over @unknown case _ in diagnostics ... (and fix-its)	2018-04-05 17:54:49 -07:00
Jordan Rose	2a0f9c3eb0	'@unknown' can match unknown cases in nested positions ... That is, when matching non-frozen enums at non-top-level positions: switch (nonFrozenEnum1, nonFrozenEnum2) { case (.singleKnownCase1, .singleKnownCase2): ... unknown: ... } ...it's sufficient to use '@unknown' to match (.singleKnownCase1, .someFutureCase2) (.someFutureCase1, .singleKnownCase2) (.someFutureCase1, .someFutureCase2)	2018-04-05 16:35:15 -07:00
Jordan Rose	7ba6ed62b2	Don't require '@unknown' in playgrounds or in the debugger ... We still model the enums as non-exhaustive so that someone /can/ handle unknown cases, which may be important for imported enums. But we won't diagnose a problem if the only missing case is '@unknown'.	2018-04-05 16:35:14 -07:00