I ran into a small edge-case where -no-alias-deps seems to report a dependency for what I expected to be an alias (so this isn't critical as it's less precise but not incorrect!)
Given lib.ml which exposes an alias to a module A:
and another module which re-exports the alias:
codept -no-alias-deps reports a dependency on Lib and on A, but I expected an alias for the later as module A2 = Lib.A1 = A (such that the compiler doesn't require A).
I ran into a small edge-case where
-no-alias-depsseems to report a dependency for what I expected to be an alias (so this isn't critical as it's less precise but not incorrect!)Given
lib.mlwhich exposes an alias to a moduleA:and another module which re-exports the alias:
codept -no-alias-depsreports a dependency onLiband onA, but I expected an alias for the later asmodule A2 = Lib.A1 = A(such that the compiler doesn't require A).