Skip to content

Overapproximation for transitive alias #49

@art-w

Description

@art-w

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:

module A1 = A

and another module which re-exports the alias:

open Lib
module A2 = A1

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions