On Thursday, 1 September 2016 at 16:38:15 UTC, Dicebot wrote:
On 09/01/2016 07:17 PM, ZombineDev wrote:
On Thursday, 1 September 2016 at 12:06:21 UTC, Dicebot wrote:
On 08/31/2016 01:01 PM, Atila Neves wrote:
And never mind that any such low level library would suffer
from the same problem unit-threaded did until dub fixed it:
D can't reflect on packages so a program must be written
that explicitly lists all modules that need to be looked at.
I don't even think fixing package reflection would truly help
here because there exist legit D projects that don't
transitively import all modules from `main` and recursive
compile-time visiting of all symbols would miss them.
[snip]
Not a problem, since you can do things like this:
It is exactly _THE_ problem. You can't have the imaginary test
runner to reliably find all tests automatically, at least all
compiled modules have to be listed explicitly. This is not
good, thus I am inclined to call extending RTTI an only viable
long-term solution.
Ooh, I thought that by "fixing package reflection" Atila meant
the ability to get a list of all modules/packages that the
compiler knows about, assuming an all at once compilation. For
things like dynamic libraries and incremental compilation,
there's obviously no other way than RTTI. But for many use-cases
CT reflection should be enough.
