• beyar-123 hotmail.com (5/12) Oct 07 2019 No, I literally killed the process and rerun dub again, how have
• H. S. Teoh (13/23) Oct 07 2019 [...]

beyar-123 hotmail.com <Beyar-123 hotmail.com> writes:

https://forum.dlang.org/post/nnwxjluqodqayihrdkqt forum.dlang.org

On Friday, 12 July 2019 at 16:23:35 UTC, 0xEAB wrote:
 On Thursday, 27 June 2019 at 15:50:43 UTC, BN26 wrote:
 Amazing work! I was looking for something like this.

 At the moment, I have to rerun dub after every change, it's a 
 pain to develop with Vibe.d

 Hey, nice to hear it's useful to you :)

 Do you already have something similar in use?


No, I literally killed the process and rerun dub again, how have 
this not been fixed yet?
Iterative and incremental development is impossible with vibe.d.

"H. S. Teoh" <hsteoh quickfur.ath.cx> writes:

On Mon, Oct 07, 2019 at 10:21:08PM +0000, beyar-123--- via
Digitalmars-d-announce wrote:
[...]
 On Thursday, 27 June 2019 at 15:50:43 UTC, BN26 wrote:
 Amazing work! I was looking for something like this.
 
 At the moment, I have to rerun dub after every change, it's a pain
 to develop with Vibe.d



[...]
 Do you already have something similar in use?


 
 No, I literally killed the process and rerun dub again, how have this
 not been fixed yet?
 Iterative and incremental development is impossible with vibe.d.

Dub leaves a lot to be desired as a build system. I gave up using dub
for my vibe.d project a long time ago. Instead, I create a fake empty
dub project in a subdirectory whose sole purpose is to declare
dependency on vibe.d, then I run dub only once in that subdirectory when
I want to update vibe.d.  The rest of the time, I use my own build
system to do the actual build/link.

My turnaround time was significantly improved by doing this.


T

-- 
People demand freedom of speech to make up for the freedom of thought which
they avoid. -- Soren Aabye Kierkegaard (1813-1855)