[Issue 17775] dmd master __VERSION__ should match the major release that it will be for

[via Digitalmars-d-bugs]

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

--- Comment #2 from Jonathan M Davis <issues.dlang at jmdavisProg.com> ---
(In reply to ZombineDev from comment #1)
> This was changed in https://github.com/dlang/dmd/pull/6935.

Drat. Well, I can't say that I understand how all of that stuff with the
release process works and how dmd knows what its version is, but the fact that
__VERSION__ for master is not a higher number than the latest release is a
definite problem for any code that needs to do something differently with
master due to upcoming changes or whatnot. I ran into this problem recently
when making some changes to vibe.d.

--