module dependency question

--0000000000001a70420656ba11ab
Content-Type: text/plain; charset="UTF-8"

I have been labouring under the mis-apprehension that the global Path.t's
within the typed AST are sufficient to identify all dependencies of a
module.
But I think the following case illustrates differently:

consider a toplevel definition:
let v = M.f ()
where M.f: unit -> N.t

the dependency on M is clear but because the value v is not inspected in
any way, the type N.t is not a dependency unless going, say, beyond the
type AST description and iterating over the term's exp_type: typexpr
looking for global Path.t's.

Is this reasonable or is there a better way of going about identifying ALL
dependencies?

--0000000000001a70420656ba11ab
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I have been labouring under the mis-apprehension that=
 the global Path.t&#39;s within the typed AST are sufficient to identify al=
l dependencies of a module.</div><div>But I think the following case illust=
rates differently:</div><div><br></div><div>consider a toplevel definition:=
</div><div>let v =3D M.f ()</div><div>where M.f: unit -&gt; N.t</div><div><=
br></div><div>the dependency on M is clear but because the value v is not i=
nspected in any way, the type N.t is not a dependency unless going, say, be=
yond the type AST description and iterating over the term&#39;s exp_type: t=
ypexpr looking for global Path.t&#39;s.=C2=A0</div><div><br></div><div>Is t=
his reasonable or is there a better way of going about identifying ALL depe=
ndencies?</div></div>

--0000000000001a70420656ba11ab--