On Wednesday, 5 September 2018 at 01:58:50 UTC, Jonathan M Davis
wrote:
On Tuesday, September 4, 2018 7:18:17 PM MDT James Blachly via
Digitalmars-d wrote:
[...]
This is part of why it's sometimes been discussed that we need
a way to indicate which dub packages are currently maintained
and work. A package updated last in February of 2016 may very
well still work today with the latest compiler, or it may fail
to compile as happens here. It depends on what the code is
doing, what has changed in D since the last update, and how
up-to-date the code really was when it was last updated (e.g.
if it was ignoring deprecation warnings rather than fixing
them, which I think was the case here).
[...]
Wouldn´t be interesting to specify the compiler version on
dub.json?
(I think ruby uses this idea)