Quite quickly: I favor the proposal, but not for its stated reasons.
In isolation it’s not a big deal to have implicit-self or to not have implicit-self. It does offer real conveniences, albeit ones that are IMHO rather small-and-petty. Given that, I think implicit self isn’t worth having if it gets in the way of higher-value features, and at least to my eyes that’s already happening. Consider that both the "method-chaining" and the “introduce-new-scope-with-new-self” proposals have, to my read, stalled due to the apparent lack of any suitable syntax for them that’s: - concise enough to be useful - unambiguous enough to be implementable-and-usable - in-line with / behaving-analogously-to the rest of the language …with the concise syntax ideas being ambiguous largely due to issues either caused-by or made substantially-more-difficult due to implicit-self. I could be mischaracterizing the issues those proposals encountered — in which case I apologize — but even so, this kind of consideration is why I’d be in favor of dropping implicit-self; I suspect it either complicates or rules-out too many other useful things to really "pay it’s own way". > On Dec 16, 2015, at 12:55 PM, Douglas Gregor via swift-evolution > <[email protected]> wrote: > > Hello Swift community, > > The review of “Require self for accessing instance members” begins now and > runs through Sunday, December 20th. The proposal is available here: > > > https://github.com/apple/swift-evolution/blob/master/proposals/0009-require-self-for-accessing-instance-members.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0009-require-self-for-accessing-instance-members.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> > > Cheers, > Doug Gregor > Review Manager > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
