Gibs could have a notion of a Module: a defined package (usually a library) that can be included easily into other C++ applications (also build using gibs). An application could specify:
//i import path/to/module.gibs
// or
//i import github.com/user/repo.git
Seeing this, gibs would automatically parse the module and include necessary headers and libraries (if any). When pointed to a remote repository, it would first clone it and then do that work. In this sense, modules could be similar to how Go language works.
The actual module would be just a regular gibs project. No special syntax is necessary. At least initially, because we would need to introduce some versioning etc.
Gibs could have a notion of a Module: a defined package (usually a library) that can be included easily into other C++ applications (also build using gibs). An application could specify:
Seeing this, gibs would automatically parse the module and include necessary headers and libraries (if any). When pointed to a remote repository, it would first clone it and then do that work. In this sense, modules could be similar to how Go language works.
The actual module would be just a regular gibs project. No special syntax is necessary. At least initially, because we would need to introduce some versioning etc.