Discussion: Last chance to rename .self and .Self?


(Brandon Knope) #1

July 27th is last day for breaking source changes for Swift 3...so I thought I would bring this up one final time.

Opinions:
- .self and .Self do not adequately convey what they do without some mental gymnastics
- self has somewhat two meanings (accessing a property on the type and getting the type of the object)
- We can get into a funky situation where we have self.someVar.self which looks odd (though symmetric!)
- What do we call these two selves? Postfix and prefix self? (I.e. Is it googleable?)

Ideas:
- rename to .type and .Type
- more bikeshedding? There has to be a better way to express these types other than .self and .Self

Brandon


(Adrian Zubarev) #2

You might have a look at our discussion thread. There is a huge overlap on your bikeshedding.

https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon–20160711/024439.html

···

--
Adrian Zubarev
Sent with Airmail

Am 15. Juli 2016 um 21:25:50, Brandon Knope via swift-evolution (swift-evolution@swift.org) schrieb:

July 27th is last day for breaking source changes for Swift 3...so I thought I would bring this up one final time.

Opinions:
- .self and .Self do not adequately convey what they do without some mental gymnastics
- self has somewhat two meanings (accessing a property on the type and getting the type of the object)
- We can get into a funky situation where we have self.someVar.self which looks odd (though symmetric!)
- What do we call these two selves? Postfix and prefix self? (I.e. Is it googleable?)

Ideas:
- rename to .type and .Type
- more bikeshedding? There has to be a better way to express these types other than .self and .Self

Brandon

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution


(Brandon Knope) #3

Thanks! I will take a look

Brandon

···

On Jul 15, 2016, at 3:28 PM, Adrian Zubarev via swift-evolution <swift-evolution@swift.org> wrote:

You might have a look at our discussion thread. There is a huge overlap on your bikeshedding.

https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon–20160711/024439.html

--
Adrian Zubarev
Sent with Airmail

Am 15. Juli 2016 um 21:25:50, Brandon Knope via swift-evolution (swift-evolution@swift.org) schrieb:

July 27th is last day for breaking source changes for Swift 3...so I thought I would bring this up one final time.

Opinions:
- .self and .Self do not adequately convey what they do without some mental gymnastics
- self has somewhat two meanings (accessing a property on the type and getting the type of the object)
- We can get into a funky situation where we have self.someVar.self which looks odd (though symmetric!)
- What do we call these two selves? Postfix and prefix self? (I.e. Is it googleable?)

Ideas:
- rename to .type and .Type
- more bikeshedding? There has to be a better way to express these types other than .self and .Self

Brandon

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution