Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Story for using the stdlib #5

Open
aiverson opened this issue Feb 12, 2019 · 0 comments
Open

Story for using the stdlib #5

aiverson opened this issue Feb 12, 2019 · 0 comments

Comments

@aiverson
Copy link
Collaborator

We need to figure out a good way to consume the stdlib in a separate project. This affects how the repository is structured.

I like the repository structure of having at the top level separate src/ docs/ and tests/ directories. It is nice and clean. However, it doesn't lend itself very well to inclusion in other projects.

I suspect that the easiest way to handle this is to have an init.t file at the top level to be found by require 'std' and then to have docs/ and tests/ be subfolders in the root and having additional subfolders for each module underneath root. For example, There might be a coro/ directory with a coro/init.t file which can be required by require 'std.coro' This does, however, mean that we can't have modules named docs or tests in any terra project following that project template.

In this case, we can just use a git submodule to include a version of the library, or have lit fetch dependencies based on a package manifest file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant