[swift-evolution] [Review] SE-0066: Standardize function type argument syntax to require parentheses
griotspeak at gmail.com
Fri May 6 00:26:32 CDT 2016
- What is your evaluation of the proposal?
I don't like it but +1. The possible ambiguity is somewhat compelling. I
actually think that, if this is accepted, it should be applied to closures
- Is the problem being addressed significant enough to warrant a change
I am not sure.
- Does this proposal fit well with the feel and direction of Swift?
I am not sure
- 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?
I read it when it first showed up and have thought about it since while
writing and reading swift.
On Thu, Apr 28, 2016 at 4:19 PM, Brent Royal-Gordon via swift-evolution <
swift-evolution at swift.org> wrote:
> > • What is your evaluation of the proposal?
> I think this change is overly fussy, but not the end of the world.
> I enjoy this convenience, but I can live without it. I hope that, when the
> dust settles from all our parameter changes, we can reintroduce it in some
> > • Is the problem being addressed significant enough to warrant a
> change to Swift?
> It seems insignificant to me, but I support small syntax clean-ups in
> > • Does this proposal fit well with the feel and direction of Swift?
> Arguably it does, at least for the current parameter-handling retrenchment.
> > • 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?
> Participated in previous discussion.
> Brent Royal-Gordon
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution