On Tue, 2019-11-19 at 10:32 +0000, Joseph Rushton Wakeling via Digitalmars-d- announce wrote: > […] > > I'm simply concerned that if we don't put enough scrutiny on the > app features and behaviour, we run the risk of simply reproducing > some of the problematic design decisions of the existing tool. > > As an example -- try running `dub test --build=release`. > Intuition suggests that this is testing a release build. But > actually it strips out your unittests, because `--build=release` > determines not only the optimization flags, but the complete set > of DFLAGS used -- and `-unittest` isn't among them. > > I ran `dub test && dub test --build=release` as a matter of habit > for some time before discovering the latter wasn't actually > testing anything. And while I now know that I _can_ define a > custom build to get what I want, that's clumsy and hard(er) to > discover, and annoying to have to repeat for every project I > create. > > That's the kind of usability and design concern we really ought > to be revisiting in any rewrite.
How can I not agree with this being a critical bug in Dub! :-) -- Russel. =========================================== Dr Russel Winder t: +44 20 7585 2200 41 Buckmaster Road m: +44 7770 465 077 London SW11 1EN, UK w: www.russel.org.uk
signature.asc
Description: This is a digitally signed message part