> Compile my public nim files to make sure they are all syntactically correct.
> Again, the hurdle appears to be identifying the files.
If by "public nim files" you mean files exposed for import by other packages,
nimble seems to have a rule for this: put all non-public files in a source
directory named _private_.
> Model dependencies between targets
It isn't as dynamic as make's, but if it counts as "target dependency modeling"
for you, you can use this:
before test:
exec "nimble buildTests"
after is also available.
> Extract code from my README and compile it
This could be done in a source file instead of a nims/nimble script by
statically reading the README, extracting the source code snippets and building
an AST from them via macro. After all, with regular source files, we make the
compiler suck them in with import statements and don't piece them together in
the build script.
