[swift-evolution] [Review] SE-0172: One-sided Ranges

[Colin Barrett]

Most of the proposal looks fine to me. A welcome feature. Eager to see
anyone's ideas for further extension to the range DSL—perhaps this will
spark people's imaginations
http://matt.might.net/articles/parsing-with-derivatives/

My only comment is concern over leaving out ..< It's not the prettiest
operator, true, but in the name of consistency and the "principle of least
surprise" I think it's the right one to use. I'm trying to imagine
explaining this to someone learning Swift—"... means up to and including
(except when it doesn't.)" Sounds like a mini-nightmare to me.

Cheers,
-Colin

On Tue, Apr 18, 2017 at 12:40 AM Douglas Gregor via swift-evolution <
swift-evolution at 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
>
> 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/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
>
> Thank you,
>
> -Doug
>
> Review Manager
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170421/4669a944/attachment.html>