> On Apr 20, 2017, at 6:36 AM, Matt Whiteside <mwhiteside....@gmail.com> wrote: > > I do like this proposed one-sided range syntax, but a while back it was > pointed out that it might conflict with a candidate syntax for variadic > generics. Has anything changed there?
It does conflict with the straw man syntax described in the generics manifesto: https://github.com/apple/swift/blob/master/docs/GenericsManifesto.md#variadic-generics <https://github.com/apple/swift/blob/master/docs/GenericsManifesto.md#variadic-generics> but variadic generics are a long way off and the syntax is totally up in the air. - Doug > -Matt > >> On Apr 17, 2017, at 21:40, Douglas Gregor via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >> Hello Swift community, >> >> The review of SE-0172 "One-sided Ranges" begins now and runs through April >> 23, 2017. The proposal is available here: >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0172-one-sided-ranges.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0172-one-sided-ranges.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 >> <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/0172-one-sided-ranges.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0172-one-sided-ranges.md> >> Reply text >> Other replies >> >> <https://github.com/apple/swift-evolution/pulls#what-goes-into-a-review-1>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 >> <https://github.com/apple/swift-evolution/blob/master/process.md> >> Thank you, >> >> -Doug >> >> Review Manager >> >> _______________________________________________ >> swift-evolution mailing list >> swift-evolution@swift.org <mailto: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