When passed a directory, we transpile recursively every file in that directory.
This also requires that all this information be passed to the type checker before the desugaring stage so that the type checker can build a context with information regarding the entire directory.
Description of potential solution
Modify pipeline so:
We iterate over each file, tokenizing and parsing each
We pass the produced ast node array to the type checker. It will then:
Iterate over each, building a context
Iterate over each again, type checking them
We pass the array of ast nodes and the produced context to the desugar stage, which will produce an array of core nodes.
For each core node, produce a transpiled python file.
We likely want to store a transpiled python project alongside its mamba counterpart.
Furthermore, it is also desirable to preserve the directory structure of the original project.
Therefore, when outputting python files:
We store them in the same sub-directory relative to the new parent.
Current Issue
Currently we only transpile one file at a time.
Description of the feature
When passed a directory, we transpile recursively every file in that directory. This also requires that all this information be passed to the type checker before the desugaring stage so that the type checker can build a context with information regarding the entire directory.
Description of potential solution
Modify pipeline so:
We likely want to store a transpiled python project alongside its mamba counterpart. Furthermore, it is also desirable to preserve the directory structure of the original project. Therefore, when outputting python files: