#CompileTimeDependencies and module resolution

[Alan Bateman]

On 13/01/2017 11:08, Remi Forax wrote:

> Hi Sander,
> you're right, it's a bug, --add-modules should not be necessary.
>
> Rémi
I don't think there is a bug here. Instead the example that Sander has 
chosen doesn't resolve a module that `requires B`. The "Notes" section 
in #CompileTimeDependences proposal has the rational for this. If the 
example is extended to:

module A { requires static B; requires C; }
module B { ... }
module C { requires B; }

then the resulting module graph will have contain at least A, B and C, 
and A will read at least B and C.

-Alan