I'm glad you like it! I agree, it does lose the at-a-glace view of all cases. That's probably something you could still get with code-folding in the IDE, but it's still something you give up for this syntax. I would hope the small cost actually helps people stick with the old syntax for small enums, and consider this for more verbose cases.
> On Jan 12, 2017, at 11:15 AM, Jay Abbott <[email protected]> wrote: > > Thanks for pointing this out Tim. I had actually read the whole thread but > over a few days between other things and must have missed the relevant > updates. > > I think you may be reacting to the very first draft. `extension` isn't used > at all in the newest draft, and no code can exist outside the enum. In fact, > there's a fair amount of similarity to your idea in the newest proposal. > > https://gist.github.com/timshadel/5a5a8e085a6fd591483a933e603c2562 > <https://gist.github.com/timshadel/5a5a8e085a6fd591483a933e603c2562> > > > Oh yes - this is much better! Lovely in fact. Although it does lose the > benefit of at-a-glance understanding of the cases present in the enum when > they are on one line each (when the code gets bigger than in the example they > will be quite a way apart).
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
