Skip to content

Check how the dependency walker handles recursive dependencies and if we should catch them as an error #37

@RupertAvery

Description

@RupertAvery

Currently, the dependency walker should stop processing a node if it has already "seen" it.

This is accomplished by assigning a unique Id (just an incrementing number for each module passed to Compile).

We just need to document the effects of having two modules reference each other directly, or through other modules.

graph TD
    A[ModuleA] --> B[ModuleB]
    A[ModuleA] --> C[ModuleC]
    B[ModuleB] --> C[ModuleC]
    C[ModuleB] --> B[ModuleC]
Loading
graph TD
    A[ModuleA] --> B[ModuleB]
    A[ModuleA] --> C[ModuleC]
    B[ModuleB] --> D[ModuleD]
    C[ModuleC] --> B[ModuleB]
    D[ModuleD] --> C[ModuleC]
Loading

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