[swift-evolution] [Pitch] Introducing #fileName debug identifier
Pierre Monod-Broca
pierremonodbroca at gmail.com
Sun Mar 13 12:12:36 CDT 2016
TLDR: a path relative to the project would be nice.
I agree an absolute path is often too much.
I don't have much file name overlap, but would it happen I reckon I would be glad to be able to differentiate them.
Pierre
> Le 13 mars 2016 à 05:07, Erica Sadun via swift-evolution <swift-evolution at swift.org> a écrit :
>
>
>> On Mar 12, 2016, at 8:27 PM, Dmitri Gribenko <gribozavr at gmail.com> wrote:
>> It should be OK to have multiple files with the same name in the
>> project. For example, in the Swift compiler we have Decl.cpp in both
>> Clang and Swift. It is important to distinguish these in the
>> assertion messages.
>>
>> Thus, I'd suggest to consider instead passing the project directory to
>> the compiler, so that the compiler can provide a file name relative to
>> the project root.
>
> Agreed that name overlap is possible. I tend to use a lot of shared code
> with "add reference" vs "add file" and relative-to-project-root actually
> ends up longer that way than just absolute path.
>
> -- Erica
>
> _______________________________________________
> 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/20160313/5b00f955/attachment.html>
More information about the swift-evolution
mailing list