[swift-evolution] [Review] SE-0087: Rename lazy to @lazy

[Ash Furrow]

* What is your evaluation of the proposal?

I’m -1 on this. The only motivation given for the proposal is:

> Swift's rule for attribues/keywords is that keywords usually modify type of variable; attributes do not.

Chris Lattner has [refuted this](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160516/017905.html):

> the proposal is incorrect in this claim

It seems then that this is largely a stylistic change. If I recall correctly, early beta versions of Swift used @lazy before removing the @. Seems unwise to revert without sound motivation.

* Is the problem being addressed significant enough to warrant a change to Swift?

It’s a stylistic change, I don’t think there’s anything wrong with the current style, so I don’t think it’s addressing an actual problem, just a stylistic choice.

* Does this proposal fit well with the feel and direction of Swift?

Not particularly.

* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

N/A

* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

I gave it a thorough reading and consideration. Admittedly I think the current style is better than the proposed @lazy, but that’s a subjective opinion.

-- 
Ash Furrow
Sent with Airmail

On May 17, 2016 at 11:31:53 PM, Chris Lattner via swift-evolution (swift-evolution at swift.org) wrote:

Hello Swift community,

The review of "SE-0087: Rename lazy to @lazy" begins now and runs through May 23. The proposal is available here:

https://github.com/apple/swift-evolution/blob/master/proposals/0087-lazy-attribute.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.

What goes into a review?

The goal of the review process is to improve the proposal under review through constructive criticism and contribute to 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,

-Chris Lattner
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/20160518/58e9d758/attachment.html>