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

[davesweeris at mac.com]

Same here
> On Jan 29, 2016, at 11:49, Adrian Kashivskyy via swift-evolution <swift-evolution at swift.org> wrote:
> 
>> What is your evaluation of the proposal?
> 
> I'm +1 on this. In my opinion it aligns well with other static compiler directives such as `#selector`, `#available`, #if`.
> 
>> Is the problem being addressed significant enough to warrant a change to Swift?
> 
> Yes, those identifiers are used often when debugging (especially logging).
> 
>> Does this proposal fit well with the feel and direction of Swift?
> 
> Definetely yes. It removes yet another C artifact which cannot be justified in any way except of familiarity. Also, `#`-prefixed keywords fit well with other compiler expressions (this argument was mentioned in the proposal itself).
> 
>> If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> 
> Obviously, in C family languages. As C family libraries and frameworks tend to name their basic constants using `__SCREAMING_SNAKE_CASE__` format so that `__FILE__` fits well among them, it is not the case in Swift.
> 
> Pozdrawiam – Regards,
> Adrian Kashivskyy

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