> On 20. Dec 2017, at 14:36, Karl Wagner <razie...@gmail.com> wrote: > > > >> On 19. Dec 2017, at 23:58, Ted Kremenek via swift-evolution >> <email@example.com <mailto:firstname.lastname@example.org>> wrote: >> >> The review of "SE 0192 - Non-Exhaustive Enums" begins now and runs through >> January 3, 2018. >> >> The proposal is available here: >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0192-non-exhaustive-enums.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0192-non-exhaustive-enums.md> >> Reviews are an important part of the Swift evolution process. All review >> feedback should be sent to the swift-evolution mailing list at: >> >> https://lists.swift.org/mailman/listinfo/swift-evolution >> <https://lists.swift.org/mailman/listinfo/swift-evolution> >> or, if you would like to keep your feedback private, directly to the review >> manager. >> >> When replying, please try to keep the proposal link at the top of the >> message: >> >> Proposal link: >> https://github.com/apple/swift-evolution/blob/master/proposals/0192-non-exhaustive-enums.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0192-non-exhaustive-enums.md> >> ... >> Reply text >> ... >> Other replies >> What goes into a review of a proposal? >> >> The goal of the review process is to improve the proposal under review >> through constructive criticism and, eventually, determine the direction of >> Swift. >> >> When reviewing a proposal, here are some questions to consider: >> >> What is your evaluation of the proposal? >> >> > +1, it needs to happen (and ASAP, since it _will_ introduce source-breaking > changes one way or the other). > > I think non-exhaustive is the correct default. However, does this not mean > that, by default, enums will be boxed because the receiver doesn’t know their > potential size? That would mean that the best transition path for > multi-module Apps would be to make your enums @exhaustive, rather than adding > “default” statements (which is unfortunate, because I imagine when this > change hits, the way you’ll notice will be complaints about missing “default” > statements).
Hah, okay, this was answered. Mail split the threads. - Karl
_______________________________________________ swift-evolution mailing list email@example.com https://lists.swift.org/mailman/listinfo/swift-evolution