Whoops. +swift-evolution ~Robert Widmann
2016/07/12 22:34、Chris Lattner <[email protected]> のメッセージ: > You can respond on list as part of the swift team if you’d like :-) > > -Chris > >> On Jul 12, 2016, at 10:33 PM, Robert Widmann <[email protected]> >> wrote: >> >> * What is your evaluation of the proposal? >> >> +1. The less optional promotion the better. >> >> * Is the problem being addressed significant enough to warrant a change to >> Swift? >> >> Yes. Removing this kind of coercion has, as I understand it, long been a >> goal. It doesn't serve much purpose outside of being slightly more >> convenient at the expensive of being terribly unreadable and downright >> confusing to reason about. >> >> * Does this proposal fit well with the feel and direction of Swift? >> >> Yes. >> >> * If you have used other languages or libraries with a similar feature, how >> do you feel that this proposal compares to those? >> >> Nothing comes to mind. >> >> * How much effort did you put into your review? A glance, a quick reading, >> or an in-depth study? >> >> Attempted an implementation last night. >> >>> On Tue, Jul 12, 2016 at 10:25 PM, Chris Lattner via swift-evolution >>> <[email protected]> wrote: >>> Hello Swift community, >>> >>> The review of "SE-0123: Disallow coercion to optionals in operator >>> arguments" begins now and runs through July 19. The proposal is available >>> here: >>> >>> >>> https://github.com/apple/swift-evolution/blob/master/proposals/0123-disallow-value-to-optional-coercion-in-operator-arguments.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 >>> [email protected] >>> https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
