[swift-evolution] [Review] SE-0121: Remove `Optional` Comparison Operators

Adrian Zubarev adrian.zubarev at devandartist.com
Tue Jul 12 13:40:49 CDT 2016


What is your evaluation of the proposal?

I probably never came across these Optional comparison operators in any Swift code I’ve been working with. The removal of these doesn’t hurt any of my codebase, so I’d appreciate less noise inside sdtlib.
Is the problem being addressed significant enough to warrant a change to Swift?

I’d say it is. As the proposal clearly stated, reintroducing these operators later would be purely additive.
Does this proposal fit well with the feel and direction of Swift?

I feel like it does, because right now these operators are more likely useless.
If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

None that I can remember of.
How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

Carefully read the proposal on GitHub.


-- 
Adrian Zubarev
Sent with Airmail

Am 12. Juli 2016 um 20:26:34, Chris Lattner via swift-evolution (swift-evolution at swift.org) schrieb:

Hello Swift community,

The review of "SE-0121: Remove `Optional` Comparison Operators" begins now and runs through July 19. The proposal is available here:

https://github.com/apple/swift-evolution/blob/master/proposals/0121-remove-optional-comparison-operators.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/20160712/913ad28b/attachment.html>


More information about the swift-evolution mailing list