[swift-evolution] [swift-evolution-announce] [Review #2] SE-0091: Improving operator requirements in protocols

[Robert Widmann]

> 	* What is your evaluation of the proposal?

+1.  Improved type checker performance for operator overloads alone is enough for me.  Improved locality of implementation is the cherry on top.

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

Absolutely.  This means protocols can be reorganized around operators without cluttering the global space space.

> 	* Does this proposal fit well with the feel and direction of Swift?

Yes.

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

The only other language I can think of that does this is C++.  

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

Talked to Doug about it this morning.

> On Jul 7, 2016, at 10:54 AM, Chris Lattner <clattner at apple.com> wrote:
> 
> Hello Swift community,
> 
> The second review of "SE-0091: Improving operator requirements in protocols" begins now and runs through July 12. The proposal is available here:
> 
> 	https://github.com/apple/swift-evolution/blob/master/proposals/0091-improving-operators-in-protocols.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-announce mailing list
> swift-evolution-announce at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce