[swift-evolution] [swift-evolution-announce] [Review] SE-0037 Clarify interaction between comments & operators

Jordan Rose jordan_rose at apple.com
Fri Mar 11 13:29:28 CST 2016

I can't agree that /*…*/ comments are useless. The examples in the proposal aren't things I would write, but I can certainly think of other places I use them.

if foo > 0 {
} else if foo < 0 {
} else /* foo == 0 */ {

// We can't use SpecificType here because of XXX.
let foo: protocol<OtherType/*, SpecificType*/> = bar()

…and then given that we have /**/ comments in the language, we should define their behavior even in places you and I personally don't intend to write them.


> On Mar 11, 2016, at 10:32 , David Owens II via swift-evolution <swift-evolution at swift.org> wrote:
> +1 for the chosen path of the proposal.
> However, one alternative is to remove /* ... */ style comments all together. Every example in the proposal are examples of commenting style that really have no business in the code.
> -David
>> On Mar 11, 2016, at 10:12 AM, Dave via swift-evolution <swift-evolution at swift.org> wrote:
>> I’m sorta in favor… Reading the proposal, I agree that something needed to be done, but I think a better solution would’ve been to disallow comments between operators and their operands. Sorry, I didn’t see the thread about it, or I would’ve said something there.
>> Anyway, if it’s this vs leaving it alone, then +1 for this.
>> -Dave Sweeris
>>> On Mar 11, 2016, at 12:00 PM, Chris Lattner <clattner at apple.com> wrote:
>>> Hello Swift community,
>>> The review of “Clarify interaction between comments & operators” begins now and runs through March 15, 2016. The proposal is available here:
>>> 	https://github.com/apple/swift-evolution/blob/master/proposals/0037-clarify-comments-and-operators.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. When replying, please try to keep the proposal link at the top of the message:
>>> 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 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
>>> Review Manager
>>> _______________________________________________
>>> swift-evolution-announce mailing list
>>> swift-evolution-announce at swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-evolution-announce
>> _______________________________________________
>> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160311/241f9a5a/attachment.html>

More information about the swift-evolution mailing list