Once the files module works, add a test suite that runs the library against its own source: common depends on nothing but the standard library and the analysis toolchain, domain modules do not depend on each other, nothing depends on the public surface, no cycles.
Both shipped siblings do this and it is the best documentation the project has.
Once the files module works, add a test suite that runs the library against its own source:
commondepends on nothing but the standard library and the analysis toolchain, domain modules do not depend on each other, nothing depends on the public surface, no cycles.Both shipped siblings do this and it is the best documentation the project has.