Skip to content

Source code loading #3

Description

@hazer-hazer

For now, Jacy just scans the whole directory where the root file (specified in the CLI) is located.
Of course, it must be fixed, and I see to ways to do it:

  1. Simple, but incorrect -- actually scan the whole directory for .jc files and throw away unused files at the name resolution stage
  2. Right, but complex -- run compilation of some file just after the module tree building stage

The second variant sounds right, anyway, it comes with some problems:

  • It complicates stages before the name resolution
  • It would be hard to avoid bugs in it, and as far as there's the lack of testing in Jacy, I should say I will be kind of temporarily supported

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or improvement as RFC

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions