[swift-evolution] [Review] SE-0068: Expanding Swift Self to class members and value types

[Charles Srstka]

* What is your evaluation of the proposal?

Mixed. I definitely think we need the functionality, but I think naming it “Self” may be confusing, since it means “self” and “Self” will mean two distinct things, despite varying only in the case of the first letter.

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

Definitely. As the proposal says, MyExtremelyLargeTypeName.staticMember is very unwieldy and awkward, and also fragile in case the type's name is changed.

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

I feel that if given a name other than Self, it will be. As proposed, there is a potential for confusion between “self” and “Self”.

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

Objective-C has [[self class] classMethod] but lacks type checking on it. This is an improvement.

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

Read through the whole thing.

Charles

> On Apr 20, 2016, at 12:16 PM, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hello Swift community,
> 
> The review of "SE-0068: Expanding Swift Self to class members and value types" begins now and runs through April 25. The proposal is available here:
> 
> 	https://github.com/apple/swift-evolution/blob/master/proposals/0068-universal-self.md <https://github.com/apple/swift-evolution/blob/master/proposals/0068-universal-self.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 <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, eventually, determine 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 you 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 <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/20160420/74067bff/attachment.html>