Skip to content

Handle module abbreviations better #23

@safesparrow

Description

@safesparrow

Currently when we see a module, we decide that the given file depends on all the previous files and all the files above it depend on it:

// Assume that a file with module abbreviations can depend on anything
match node.Data.Abbreviations |> Array.isEmpty |> not with
| true -> nodes |> Array.map (fun n -> n.File)

This is a safety we need without fully understanding the behaviour and implementing it.

This ticket is to avoid this defensive mechanism.

Also: module abbreviations in signature files are currently not supported, we should fix it:

failwith "Module abbreviations are not currently supported"

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