You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically the bulk of the code for Cadence is located in a directory named runtime.
This is confusing from a language perspective, as it might be confused with a language's runtime.
Also, the parser is currently located in a package called parser2, as it is the second parser for Cadence. However, given the first parser was removed, the package should be renamed.
Suggested Solution
Move all directories nested in the runtime directory to the root of the repository, e.g. ast, sema, etc.
Rename parser2 to parser
The text was updated successfully, but these errors were encountered:
It would also be good to separate out the compiler front-end and the back-end. That leaves us the freedom to plug in different compiler back-ends needed for different runtimes in future.
To start with, maybe we can move the child packages under runtime one level up, so they are siblings to the runtime package, and leave the runtime package as-is.
Issue To Be Solved
Historically the bulk of the code for Cadence is located in a directory named
runtime
.This is confusing from a language perspective, as it might be confused with a language's runtime.
Also, the parser is currently located in a package called
parser2
, as it is the second parser for Cadence. However, given the first parser was removed, the package should be renamed.Suggested Solution
runtime
directory to the root of the repository, e.g.ast
,sema
, etc.parser2
toparser
The text was updated successfully, but these errors were encountered: