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
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.
The text was updated successfully, but these errors were encountered:
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 byrequire '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.
The text was updated successfully, but these errors were encountered: