[swift-evolution] [Review] SE-0068: Expanding Swift Self to class members and value types
panajev at gmail.com
Thu Apr 21 01:06:19 CDT 2016
Don't get me started on the case insensitive file system in OS X, some programs still do not work right without it and it is a cause of errors that just piss me off... especially when you share data outside of the happy case insensitive castle :/.
[[iOS messageWithData:ideas] broadcast]
> On 21 Apr 2016, at 06:10, L Mihalkovic via swift-evolution <swift-evolution at swift.org> wrote:
> I couldn't understand for a moment why people would think that “Self" versus "self” is confusing.. and then I remembered that Apple does not (by default) distinguish file names with different casing in the filesystem… I think we either educate people or we keep them ignorant in the name of their best interest. Apple seem to regularly choose the bottom end. I hope after 40 years someone will decide it is time to look forward and embrace Self
>>> On Apr 21, 2016, at 3:14 AM, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> wrote:
>>> 1) “Self" differs from “self” by just the first letter being capitalized. Regardless of case, it is confusing for the terms “self” or “Self” or “SELF” to mean different things from within the same context.
>> What, you've never done things like this?
>> let page = Page()
>> let document = Document(pages: [page])
>> let account = Account(oAuthToken: token)
>> Brent Royal-Gordon
>> Sent from my iPhone
>> swift-evolution mailing list
>> swift-evolution at swift.org
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution