Thread overview
Compiler version "dirty"
Mar 08, 2021
Q. Schroll
Mar 09, 2021
Paul Backus
May 20, 2021
JN
May 22, 2021
Norm
March 08, 2021
When I enter `dmd --version`, it says:
  DMD64 D Compiler v2.095.1-dirty
What should the "dirty" mean? To me, it seems looks something went wrong somewhere.
March 09, 2021
On Monday, 8 March 2021 at 22:29:58 UTC, Q. Schroll wrote:
> When I enter `dmd --version`, it says:
>   DMD64 D Compiler v2.095.1-dirty
> What should the "dirty" mean? To me, it seems looks something went wrong somewhere.

It means someone made a mistake when preparing the release. Probably harmless.
May 20, 2021
On Tuesday, 9 March 2021 at 01:36:18 UTC, Paul Backus wrote:
> On Monday, 8 March 2021 at 22:29:58 UTC, Q. Schroll wrote:
>> When I enter `dmd --version`, it says:
>>   DMD64 D Compiler v2.095.1-dirty
>> What should the "dirty" mean? To me, it seems looks something went wrong somewhere.
>
> It means someone made a mistake when preparing the release. Probably harmless.

v2.096.1 also reports as -dirty
May 22, 2021

On Monday, 8 March 2021 at 22:29:58 UTC, Q. Schroll wrote:

>

When I enter dmd --version, it says:
DMD64 D Compiler v2.095.1-dirty
What should the "dirty" mean? To me, it seems looks something went wrong somewhere.

This comes from git describe --dirty and indicates there were uncommitted changes in the repo when the release was built. This would raise red flags if seen in a commercial setting and looks a bit unprofessional but it is most likely harmless. Probably one of the build scripts or unittests are polluting the repo.