[swift-evolution] [Review] SE-0028 Modernizing Swift's Debugging Identifiers (__LINE__, etc)

[Trent Nadeau]

Proposal:
https://github.com/apple/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.md

   - What is your evaluation of the proposal?
   - +1. This change makes the language more consistent in symbology and
      naming.
   - Is the problem being addressed significant enough to warrant a change
   to Swift?
   - Yes, consistency is important.
   - Does this proposal fit well with the feel and direction of Swift?
   - Yes
   - If you have you used other languages or libraries with a similar
   feature, how do you feel that this proposal compares to those?
   - Besides C/C++ from which the current names are based, I've used Rust,
      which has vary similar naming to this proposal (line!, column!,
file!). The
      exclamation point suffix there is for a macro expanded by the compiler,
      similar to the # prefix in Swift.
   - How much effort did you put into your review? A glance, a quick
   reading, or an in-depth study?
   - I've read and been involved in the swift-evolution thread from the
      beginning.


On Fri, Jan 29, 2016 at 2:31 PM, Chris Lattner via swift-evolution <
swift-evolution at swift.org> wrote:

> Hello Swift community,
>
> The review of "Modernizing Swift's Debugging Identifiers" begins now and
> runs through February 2nd. The proposal is available here:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.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, 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
>
> Thank you,
>
> -Chris Lattner
> Review Manager
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>



-- 
Trent Nadeau
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160129/3beec16a/attachment.html>