What do you find so useful about them? And in what context does it make sense to you that `nil < .some(x)` always evaluates to true? When I found that out, I was very surprised by that behaviour (just like many others). Do you have examples of then an optional comparison makes the code clearer?
> Goddammit. I completely missed this thread, because Pipermail regularly > decides not to deliver the swift-evolution-announce version of review threads > (which means they bypass my inbox). Why does it do this? Most of the emails > get delivered, but it just skips some of them, and I keep ending up missing > review threads because of it. > > This change is going to have a HUGE impact for me. I use this sort of > comparison _all the time_ and find it incredibly useful, and have had > literally zero bugs caused by this. Surely I can't be the only one who uses > this. I am not looking forward to copying&pasting a reimplementation of the > comparison functions into every single project I work on. > > I'm also really concerned about how fast such a hugely-impactful change was > proposed, accepted, and implemented. The proposal PR was submitted on July > 12, merged the same day, and a review kicked off again on the same day. And > the first thread the proposal referenced only happened the previous day, on > July 11. And the implementation landed only 12 days later on July 24th. This > was extremely fast and didn't even have time to have the proposal listed on > apple/swift-evolution for people to find before the review kicked off. It > looks like this was done so the change could be made before the end of > source-breaking changes, but the fast-tracking of something like this means > that people like me completely missed it, and now we're stuck with a > highly-impactful change that we don't want. Fast-tracking proposals is > understandable when they're largely additive, or they fix something that is > widely accepted as a problem. But being able to compare optionals is not > universally recognized as a problem, and I know for a fact I've weighed in on > this subject in the past on swift-evolution. I do not think it was > appropriate to fast-track this proposal. > > -Kevin Ballard > > On Wed, Jul 20, 2016, at 05:38 PM, Chris Lattner via swift-evolution wrote: > > Proposal Link: > > https://github.com/apple/swift-evolution/blob/master/proposals/0121-remove-optional-comparison-operators.md > > > > The review of "SE-0121: Remove Optional Comparison Operators" ran from > > Active review July 12...19. The proposal has been *accepted*. > > > > Feedback has been universally positive from both the community and the core > > team, because it eliminates a surprising part of the Swift model at very > > little utility cost. > > > > Thank you to Jacob Bandes-Storch for driving this discussion forward. > > > > -Chris Lattner > > Review Manager > > > > > > _______________________________________________ > > swift-evolution mailing list > > [email protected] > > https://lists.swift.org/mailman/listinfo/swift-evolution > > > _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
