https://issues.dlang.org/show_bug.cgi?id=14662

Johan Engelen <jbc.engelen@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jbc.engelen@gmail.com

--- Comment #1 from Johan Engelen <jbc.engelen@gmail.com> ---
Using __FILE__ as template parameter is definitely bug-prone.

Related forum discussion: https://forum.dlang.org/thread/induraqegvpyomvzxwmf@forum.dlang.org

--

https://issues.dlang.org/show_bug.cgi?id=14662

Basile-z <b2.temp@gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |b2.temp@gmx.com
         Resolution|---                         |WONTFIX

--- Comment #2 from Basile-z <b2.temp@gmx.com> ---
there's __FILE_FULL_PATH__ now

--

https://issues.dlang.org/show_bug.cgi?id=14662

johanengelen@weka.io changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johanengelen@weka.io

--- Comment #3 from johanengelen@weka.io ---
I still think this is a bug and related bugginess of __FILE__ as mentioned in the forum post. Yes there is __FILE_FULL_PATH__ but that does not help with libraries distributed in binary+.di (include files). See the forum post above for details.

--

https://issues.dlang.org/show_bug.cgi?id=14662

Basile-z <b2.temp@gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|b2.temp@gmx.com             |

--