> On 18 Feb 2017, at 14:16, David Rönnqvist via swift-evolution > <swift-evolution@swift.org> wrote: > > On 18 Feb 2017, at 09:30, Slava Pestov via swift-evolution > <swift-evolution@swift.org> wrote: > >> +1, two small questions: >> >> - If two cases have the same base name but different full names, will >> matching on the base name match both cases, or will it be an error? > > I feel that it would be safer if it was an error. If the developer intends to > match both cases, requiring both explicitly is a (slight) inconvenience but > it's also very clear about what's going to match.
Full name matching would also allow a kind of “overloading” which can be very desirable in many cases. Besides full-name matching seems more intuitive correct (compare for example case sensitivity). Rien. > >> - What are the memory layout optimizations described here? From a first >> glance this looks purely syntactic. >> >> Slava >> >>> On Feb 17, 2017, at 7:26 PM, John McCall via swift-evolution >>> <swift-evolution@swift.org> wrote: >>> >>> Hello Swift community, >>> >>> The review of "SE-0155: Normalize Enum Case Representation" begins now and >>> runs through next Friday, February 26th. The proposal is available here: >>> >>> https://github.com/apple/swift-evolution/blob/master/proposals/0155-normalize-enum-case-representation.md >>> >>> Reviews are an important part of the Swift evolution process. All reviews >>> should be sent to the swift-evolution mailing list at >>> 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/0155-normalize-enum-case-representation.md >>> >>> Reply text >>> >>> Other replies >>> >>> What goes into a review? >>> >>> The goal of the review process is to improve the proposal under review >>> through constructive criticism and, eventually, determine the direction of >>> Swift. When writing your review, here are some questions you might want to >>> answer in your review: >>> >>> • What is your evaluation of the proposal? >>> • Is the problem being addressed significant enough to warrant a change >>> to Swift? >>> • Does this proposal fit well with the feel and direction of Swift? >>> • If you have used other languages or libraries with a similar feature, >>> how do you feel that this proposal compares to those? >>> • How much effort did you put into your review? A glance, a quick >>> reading, or an in-depth study? >>> >>> More information about the Swift evolution process is available at >>> https://github.com/apple/swift-evolution/blob/master/process.md >>> >>> Thank you, >>> >>> John McCall >>> Review Manager >>> _______________________________________________ >>> 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 > _______________________________________________ > 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
