<div dir="ltr">I'm ready to submit a pull request:<div><br><div><div><div><a href="https://github.com/Anton3/swift-evolution/blob/lazy-attribute/proposals/NNNN-lazy-attribute.md">https://github.com/Anton3/swift-evolution/blob/lazy-attribute/proposals/NNNN-lazy-attribute.md</a><br></div></div><div><br></div><div>- Anton</div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-05-03 0:25 GMT+03:00 David Sweeris <span dir="ltr"><<a href="mailto:davesweeris@mac.com" target="_blank">davesweeris@mac.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yeah, I was just thinking that we should get the “call-site” syntax settled for property behaviors, for exactly that reason.<br>
<div><div class="h5"><br>
> On May 2, 2016, at 3:39 PM, Антон Жилин via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
> One of proposals that will probably be submitted for Swift 4, will be Property Behaviors propoal.<br>
><br>
> It aims to generalize @IBOutlet, @synchronized, @delayedinit, and of course, @lazy.<br>
> (Side note: it would be great if it also included unowned)<br>
><br>
> Because we aim for less breaking changes in Swift 4, we should prepare ground for it.<br>
> The suggestion is to rename `lazy` to `@lazy`.<br>
><br>
> Besides the aforementioned reason, I think, lazy really has its place among attributes.<br>
> It does not change type of property, it just helps to delay side effects of initialization.<br>
><br>
> - Anton<br>
</div></div>> _______________________________________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br>
</blockquote></div><br></div>