+1. I’ve given this a lot of thought. I always put parentheses in, so this wouldn’t really affect me. Bigger picture though I thought back on what made us not require self usage, and I feel like this proposal could be rejected for similar reasons. However, I’ve never been confused by the self syntax, but not including parenthesis has led to some mixups when reading an API. I’m probably not the only one that has happened to.
> On Apr 25, 2016, at 9:22 PM, Douglas Gregor via swift-evolution > <[email protected]> wrote: > > Hello Swift community, > > The review of SE-0066 "Standardize function type argument syntax to require > parentheses" begins now and runs through May 2, 2016. The proposal is > available here: > > https://github.com/apple/swift-evolution/blob/master/proposals/0066-standardize-function-type-syntax.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0066-standardize-function-type-syntax.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/0066-standardize-function-type-syntax.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0066-standardize-function-type-syntax.md> > Reply text > > Other replies > <https://github.com/apple/swift-evolution#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 Gregor > > Review Manager > > > _______________________________________________ > 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
