<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><span style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;">* What is your evaluation of the proposal?</span></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I’m -1 on this. The only motivation given for the proposal is:</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="margin: 0px;"><span style="color: rgb(0, 0, 0); font-family: Helvetica, Arial; font-size: 13px;">> </span>Swift's rule for attribues/keywords is that keywords usually modify type of variable; attributes do not.</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">Chris Lattner has [refuted this](<a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160516/017905.html">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160516/017905.html</a>):</div><div id="bloop_customfont" style="margin: 0px;"><br></div><div id="bloop_customfont" style="margin: 0px;">> <span style="white-space: pre-wrap;">the proposal is incorrect in this claim</span></div><div id="bloop_customfont" style="margin: 0px;"><span style="white-space: pre-wrap;"><br></span></div><div id="bloop_customfont" style="margin: 0px;"><span style="white-space: pre-wrap;">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.</span></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;"><span style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;">* Is the problem being addressed significant enough to warrant a change to Swift?</span></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">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.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;"><span style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;">* Does this proposal fit well with the feel and direction of Swift?</span></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Not particularly.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;"><span style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;">* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</span></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">N/A</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;"><span style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;">* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;"></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><span style="font-family: 'helvetica Neue', helvetica; font-size: 13.333333015441895px;"><br></span></div><div id="bloop_customfont" style="margin: 0px;"><font face="helvetica Neue, helvetica">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.</font></div> <br> <div id="bloop_sign_1463617539683068160" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Ash Furrow<br>Sent with Airmail</div></div> <br><p class="airmail_on">On May 17, 2016 at 11:31:53 PM, Chris Lattner via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Hello Swift community,<br><br>The review of "SE-0087: Rename lazy to @lazy" begins now and runs through May 23. The proposal is available here:<br><br> https://github.com/apple/swift-evolution/blob/master/proposals/0087-lazy-attribute.md<br><br>Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at<br><br> https://lists.swift.org/mailman/listinfo/swift-evolution<br><br>or, if you would like to keep your feedback private, directly to the review manager.<br><br>What goes into a review?<br><br>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:<br><br> * What is your evaluation of the proposal?<br> * Is the problem being addressed significant enough to warrant a change to Swift?<br> * Does this proposal fit well with the feel and direction of Swift?<br> * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br><br>More information about the Swift evolution process is available at<br><br> https://github.com/apple/swift-evolution/blob/master/process.md<br><br>Thank you,<br><br>-Chris Lattner<br>Review Manager<br><br><br><br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote></body></html>