I included that, but also I again don't think that's the correct design. There's a case where that's useful, but that shouldn't be the default, and I don't think it's important enough to do in Swift 5.
Jordan > On Jan 12, 2018, at 15:15, Dave DeLong <sw...@davedelong.com> wrote: > > Unless I’m missing something, this is still missing the discussion on being > able to treat all enums of internally-packaged libraries as frozen. > > IE, that frozen vs unfrozen is only an issue for enums that come from modules > that are not packaged with your app. > > Dave > >> On Jan 12, 2018, at 4:08 PM, Jordan Rose via swift-evolution >> <swift-evolution@swift.org> wrote: >> >> Okay, I went back to `unknown case` in the proposal, but mentioned Chris's >> point very specifically: if the compiler emits an error, we should go with >> `case #unknown` instead. (I'm very strongly in the "warning" camp, though.) >> >> I think the revised proposal is in good shape! >> (https://github.com/apple/swift-evolution/pull/777) I think I've addressed >> everyone's feedback either in the proposal or on-list, if not necessarily >> convinced them. If there are no other major comments I'll let Ted know that >> it's ready to re-run on Monday. >> >> Jordan >> _______________________________________________ >> swift-evolution mailing list >> swift-evolution@swift.org >> https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
