> P.S. I really liked the idea to use a dot instead of dot self but yeah, dot > is already reserved for enums.
FWIW This isn’t enum-specific — the dot shortcut syntax works for any type member of a type, but only in contexts where you’re passing a value. Correct me if I’m wrong, I believe the ambiguity is that you can start a line with a dot when you split a method call/property access chain into multiple lines and want to continue calling methods on the last line’s value. — Radek > On 17 Dec 2015, at 23:38, Rudolf Adamkovic via swift-evolution > <[email protected]> wrote: > > After careful reading through all the arguments, I'm now in the -1 camp too. > > The "visual noise" examples and reasoning about consistency with the rest of > the language totally got me. > > P.S. I really liked the idea to use a dot instead of dot self but yeah, dot > is already reserved for enums. > > R+ > > Sent from my iPhone > > On 16 Dec 2015, at 19:55, Douglas Gregor via swift-evolution > <[email protected] <mailto:[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] <mailto:[email protected]> >> https://lists.swift.org/mailman/listinfo/swift-evolution >> <https://lists.swift.org/mailman/listinfo/swift-evolution> > > _______________________________________________ > 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
