On Friday, 22 April 2016 at 18:18:39 UTC, Basile B. wrote:
I think a DMD option should be added to allow the tests to be
compiled but never called, something like -runTests. Because
the first solution is much more attractive.
Actually the first solution works with:
https://dlang.org/phobos/co
On Thursday, 21 April 2016 at 19:38:21 UTC, Nordlöw wrote:
On Thursday, 21 April 2016 at 12:35:42 UTC, Anonymouse wrote:
Then dmd -unittest -version=TestDeps if you want them run.
This doesn't make things easier. I want to disable the builtin
unittests of the modules I've imported. This requi
On Thursday, 21 April 2016 at 12:35:42 UTC, Anonymouse wrote:
Then dmd -unittest -version=TestDeps if you want them run.
This doesn't make things easier. I want to disable the builtin
unittests of the modules I've imported. This requires me to add a
version(test_MODULE) unittest
in each mod
On Monday, 21 March 2016 at 10:29:36 UTC, Nordlöw wrote:
I want to enable unittests only at the top-level of a module
compilation.
If I have a module
top.d
that imports
dep1.d
dep2.d
...
which all contain unittests, how do I compile top.d with only
the unittests for top.d e
On Monday, 21 March 2016 at 15:25:29 UTC, Adam D. Ruppe wrote:
Yes, compiling 33,000 lines from my libs happened in about one
second.
My experience with slow D builds tends to be that it is caused
by CTFE, not by scale.
These kinds of modules are very different from the ones I'm
working on.
On Monday, 21 March 2016 at 15:15:41 UTC, Nordlöw wrote:
This is because my project has grown beyond 30klines of code
and at that scale not even D's speed is enough for getting fast
incremental builds through dmd.
Note that lines of code isn't really important to build time...
$ time dmd -c -
On Monday, 21 March 2016 at 15:15:41 UTC, Nordlöw wrote:
I don't see any other solution for really large projects.
Except implementing memoized execution of unittests into dmd.
Which I have discussed previously :)
On Monday, 21 March 2016 at 15:11:31 UTC, Nordlöw wrote:
On Monday, 21 March 2016 at 11:36:10 UTC, wobbles wrote:
This is quite annoying I feel.
There probably should be an option for the -unittest flag to
only compile unittests for the source files I'm passing in,
and not any of the tests in
On Monday, 21 March 2016 at 11:36:10 UTC, wobbles wrote:
This is quite annoying I feel.
There probably should be an option for the -unittest flag to
only compile unittests for the source files I'm passing in, and
not any of the tests in the -I import paths.
I very much agree.
On Monday, 21 March 2016 at 10:37:31 UTC, ZombineDev wrote:
On Monday, 21 March 2016 at 10:29:36 UTC, Nordlöw wrote:
I want to enable unittests only at the top-level of a module
compilation.
If I have a module
top.d
that imports
dep1.d
dep2.d
...
which all contain unittests
On Monday, 21 March 2016 at 10:29:36 UTC, Nordlöw wrote:
I want to enable unittests only at the top-level of a module
compilation.
If I have a module
top.d
that imports
dep1.d
dep2.d
...
which all contain unittests, how do I compile top.d with only
the unittests for top.d e
I want to enable unittests only at the top-level of a module
compilation.
If I have a module
top.d
that imports
dep1.d
dep2.d
...
which all contain unittests, how do I compile top.d with only the
unittests for top.d enabled?
12 matches
Mail list logo
