Hi Matthew, In general, if you think there is something to be updated in the proposal, it is worth creating a new revision (like in the floating point protocols proposal, for example) and mentioning it in the thread.
I think it is a way to go in this particular case, since we are still in the first half of the review period. Any further discussion would benefit from it. max > On May 5, 2016, at 4:02 PM, Matthew Johnson <[email protected]> wrote: > > > > Sent from my iPhone > > On May 5, 2016, at 5:19 PM, Max Moiseev via swift-evolution > <[email protected] <mailto:[email protected]>> wrote: > >> Hi all, >> >> This email is the result of a discussion between members of the standard >> library team. >> >> We suggest changing the initializers argument label to `exactly` to match >> the one used in the floating point protocols proposal >> <https://github.com/apple/swift-evolution/blob/master/proposals/0067-floating-point-protocols.md>. >> Other than that the proposal seems to be a valuable addition to the >> standard library. > > Thanks Max. I'm glad to hear that! Should I update the proposal or will you > just make that change as part of "accepted with modification"? > >> >> max >> >>> On May 3, 2016, at 8:57 PM, Chris Lattner <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hello Swift community, >>> >>> The review of "SE-0080: Failable Numeric Conversion Initializers" begins >>> now and runs through May 9. The proposal is available here: >>> >>> >>> https://github.com/apple/swift-evolution/blob/master/proposals/0080-failable-numeric-initializers.md >>> >>> <https://github.com/apple/swift-evolution/blob/master/proposals/0080-failable-numeric-initializers.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 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 >>> <https://github.com/apple/swift-evolution/blob/master/process.md> >>> >>> Thank you, >>> >>> -Chris Lattner >>> Review Manager >>> >>> _______________________________________________ >>> swift-evolution-announce mailing list >>> [email protected] >>> <mailto:[email protected]> >>> https://lists.swift.org/mailman/listinfo/swift-evolution-announce >>> <https://lists.swift.org/mailman/listinfo/swift-evolution-announce> >> >> _______________________________________________ >> 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
