On Tue, 23 May 2017 10:32:06 GMT, Martin Tschierschke wrote:
On Tue, 16 May 2017 16:05:42 GMT, Martin Tschierschke wrote:
Now as using the latest vibe.d (0.8 beta) the build time,
when touching app.d or a .dt file has increased to app 4 seconds, app 1 second more then some releases before.Now since vibe is split in several sub packages, how to get use of this, when i do not need for example vibe-d:mongodb or
vibe-d:mail ?I am using the faster gold linker with dmd.
Regards mt.
I found a partial answer by looking at the examples:Now I use in dub.sdl:
dependency "vibe-d:http" version="~>0.7.0"
dependency "diet-ng" version="~>1.1"
versions "VibeDefaultMain"
versions "DietUseCache"and in the code:
import vibe.http.fileserver;
import vibe.http.router;
import vibe.http.server;Would be cool to know the import hierarchy of vibe.d.
I thought about that too recently, because especially now that the sub packages get broken out into full packages it will be pretty important to know which package contains which module anyway. Also, each package will have an own version, which also will have to be reflected in the API documentation on vibed.org.
Regardless of the sub package topic, I'll have to, at some point, repeat the procedure that Vladimir Panteleev (cybershadow) once initiated. He wrote a tool that approximates the time taken in the parser/semantic/codegen phases of the compiler for each module, so that it becomes visible where the compile time performance hogs are. That would hopefully allow bringing down the build times to earlier numbers.