Furrow
https://ashfurrow.com/
On December 21, 2017 at 1:55:40 PM, Jordan Rose (jordan_r...@apple.com) wrote:
Thanks for your response, Ash. Comments inline.
On Dec 20, 2017, at 11:49, Ash Furrow via swift-evolution
wrote:
Proposal link:
https://github.com/apple/swift-evolution/blob/master
Proposal link:
https://github.com/apple/swift-evolution/blob/master/proposals/0192-non-exhaustive-enums.md
What is your evaluation of the proposal?
-1.
Is the problem being addressed significant enough to warrant a change to Swift?
I’m afraid not.
>From my perspective as a Swift user, this ch
* What is your evaluation of the proposal?
+1 from me. I particularly like how this adheres to the principle of least
surprise. Keeping == and != is an important part of the proposal, as others
have said.
* Is the problem being addressed significant enough to warrant a change to
Swift?
I beli
* What is your evaluation of the proposal?
I’m -1 on this. The only motivation given for the proposal is:
> Swift's rule for attribues/keywords is that keywords usually modify type of
> variable; attributes do not.
Chris Lattner has [refuted
this](https://lists.swift.org/pipermail/swift-evolut