A few questions:

1. What is universal lookup? How is this different than the compiler having to 
search a crowded namespace? I'm really trying to understand how this is making 
it easier for the type checker. 

2. If operators are a special case, why not replace static/class func with an 
"operator" keyword? Requiring static/class seems like an implementation detail 
to get this universal lookup. 

3. Will the static vs class distinction ever be fixed or cleaned up? Isn't 
there a way to share one keyword for this same feature across all types?

Regardless, I'm still giving this a +1. 

I'm just hoping we can:
- reduce some cognitive burden
- add a little character 

Brandon 

> On Jul 7, 2016, at 1:54 PM, Chris Lattner <[email protected]> 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
> [email protected]
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to