On Sunday, 3 November 2019 at 13:35:36 UTC, Martin Nowak wrote:
> Glad to announce D 2.089.0, ♥ to the 44 contributors.
>
> This release comes with corrected extern(C) mangling in mixin templates, atomicFetchAdd and atomicFetchSub in core.atomic, support for link driver arguments, better support of LDC in dub, and plenty of other bug fixes and improvements.
>
> http://dlang.org/download.html
> http://dlang.org/changelog/2.089.0.html
>
> -Martin

My code hit a regression on 2.089.

This worked fine, before dmd 2.089 (reduced):

mixin Bug!"asd";

enum test;

template Bug(string n)
{
   int main()
   {
         import std;
         foreach(name;  __traits(allMembers,  __traits(parent, main)))
            static if (hasUDA!(__traits(getMember, __traits(parent, main), name), test))
               return 0;

         return 0;
   }
}

On Thursday, 7 November 2019 at 16:37:56 UTC, Andrea Fontana wrote:
> On Sunday, 3 November 2019 at 13:35:36 UTC, Martin Nowak wrote:
>> Glad to announce D 2.089.0, ♥ to the 44 contributors.
>>
>> This release comes with corrected extern(C) mangling in mixin templates, atomicFetchAdd and atomicFetchSub in core.atomic, support for link driver arguments, better support of LDC in dub, and plenty of other bug fixes and improvements.
>>
>> http://dlang.org/download.html
>> http://dlang.org/changelog/2.089.0.html
>>
>> -Martin
>
> My code hit a regression on 2.089.
>


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

On Thursday, November 7, 2019 3:25:46 AM MST Ron Tarrant via Digitalmars-d- announce wrote:
> On Wednesday, 6 November 2019 at 14:09:35 UTC, Mike Parker wrote:
> > Are you putting libs in the compiler's directory tree? Or are you editing sc.ini/dmd.conf? You really shouldn't be doing the former.
>
> I follow the steps outlined here: https://github.com/gtkd-developers/GtkD/wiki/Installing-on-Windows
>
> And one of those steps (Step #5) says to copy the gtkd libs to
> the compiler's directory tree. Is that what you mean by "You
> really shouldn't be doing the
> former."?
>
> And I also edit sc.ini.

You should pretty much never put anything in the compiler's directory tree, and there's no need to. If you're editing the sc.ini, you might as well just put your external libraries somewhere else and have sc.ini point to them there. Putting code in a directory that the installer manages provides no benefit while causing problems like the installer deleting it when updating. In most cases though, the recommended thing to do is to just use dub rather than manually mucking around with sc.ini or dmd.conf.

This reminds me of someone complaining that they couldn't just unzip the dmd install on top of another and have it work (their code no longer compiled aftery they'd just unzipped a release of dmd/phobos which had a split std.datetime on top of one that didn't).

- Jonathan M Davis