[swift-evolution] [Review] SE-0090: Remove .self and freely allow type references in expressions

[Joe Groff]

> On May 17, 2016, at 8:56 PM, T.J. Usiyan via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Could we reconsider rejecting the uppercase and lowercase conventions as a syntactic requirement? While I still disagree with enum cases not being UpperCamelCase, that decision narrows the 'approved' enough that the syntactic requirement would line up with guidance. It would also make teaching the conventions much easier. New students who, for whatever reason, prefer naming variables with upper camel case would have immediate and concrete feedback from the dev tools that that is non-idiomatic. 

Enforcing this at the language level would require us to decide how to handle importing APIs that don't follow the rules. We've put effort into modifying many of the Core Foundation APIs, but not all of them, and there's of course still POSIX and the standard C library. (We'd also need a rule for non-Western scripts that don't distinguish case.)

> 
> If that is a non starter, let me try another. Was a disambiguating token preceding the type reference considered? 

We expressly wanted to avoid anything like C++'s `typename` and `template` disambiguation hacks.

-Joe

> On Tue, May 17, 2016 at 11:33 PM, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
> Hello Swift community,
> 
> The review of "SE-0090: Remove .self and freely allow type references in expressions" begins now and runs through May 23. The proposal is available here:
> 
>         https://github.com/apple/swift-evolution/blob/master/proposals/0090-remove-dot-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
> 
> 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 mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution