[swift-evolution] [Review] SE-0024 "Optional Value Setter `??=`"

[Adrian Kashivskyy]

> What is your evaluation of the proposal?

I'm -1 on this.

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

In my opinion it's not and I even consider it an anti-pattern, like the previous debaters noticed.

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

I used a ||= operator in Ruby and I think in the Ruby's world of brevity it fits there well.

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

I thought it over many times.

Regards,
Adrian Kashivskyy
Senior iOS Developer at Netguru

> Wiadomość napisana przez Douglas Gregor via swift-evolution <swift-evolution at swift.org> w dniu 13.02.2016, o godz. 06:15:
> 
> Hello Swift community,
> 
> The review of SE-0024 "Optional Value Setter `??=`" begins now and runs through February 18, 2016. The proposal is available here:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0024-optional-value-setter.md <https://github.com/apple/swift-evolution/blob/master/proposals/0024-optional-value-setter.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/0024-optional-value-setter.md <https://github.com/apple/swift-evolution/blob/master/proposals/0024-optional-value-setter.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
> 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/20160216/be17afab/attachment.html>