Re: [swift-evolution] The Non-Exhaustive Enums proposal kills one of Swift's top features - change proposal

the existence of the ‘complete switch’ construct, they could just use normal ‘switch’ statements and miss out on the completeness checking. Thomas > On 24/12/2017, at 1:15 PM, Slava Pestov <spes...@apple.com> wrote: > > > >> On Dec 23, 2017, at 3:47 PM, Thomas Roughton via sw

Re: [swift-evolution] The Non-Exhaustive Enums proposal kills one of Swift's top features - change proposal

> On 24/12/2017, at 9:40 AM, Cheyo Jimenez via swift-evolution > wrote: > > What are your thoughts on `final switch` as a way to treat any enum as > exhaustible? > https://dlang.org/spec/statement.html#FinalSwitchStatement >

Re: [swift-evolution] [Review] SE 0192 - Non-Exhaustive Enums

Looking at the feedback to this proposal, it looks like a common thread is people wanting to make sure they’re notified when new cases are introduced (the ‘future’ keyword’). However, if I’m understanding correctly, the resistance to adding such a keyword is that it becomes complicated when