> On Feb 25, 2017, at 6:07 PM, Daniel Duan via swift-evolution > <[email protected]> wrote: > > Not sure which “this” you were referring to. The anonymous case part is > something that I consider out-of-scope for this proposal as well. It came up > during review and is posted as one of the core team’s request. There are two > possibilities regarding this feature: I can put it in future considerations > and defer it to a different proposal. Alternatively, I can write a 2-part > proposal with the 2nd part being this feature. Each part would be reviewed > separately.
Once we specify how overloaded patterns are matched (with casting) it becomes pretty straightforward that anonymous cases are matched with `(let s as String)`. I think it would good to include anonymous cases but make it clear that you view it as an “optional” enhancement that the core team is free to omit in the accepted version. I believe Dave A was the one who first mentioned it so it probably has a reasonable shot at being accepted, > >> On Feb 25, 2017, at 12:10 PM, Tino Heth via swift-evolution >> <[email protected]> wrote: >> >> Maybe I'm missing something obvious (or maybe I'm just generally in favour >> for case classes ;-), but as the main motivation for the proposal seems to >> be that enum cases should be more function-like: Why is this desirable? >> _______________________________________________ >> swift-evolution mailing list >> [email protected] >> https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
