The Slice compiler accepts 2 "kinds" of input files:
source files: for which we will actually generate codereference files: which we parse, but are only to be referenced by source files.
There is an asymmetry between these two that I'm not sure makes any sense to have.
Source files can only be passed in as individual files, while reference files can be passed as individual files, but also can be passed in by directory. In which case, we scan the directory for any .slice files and use them as references.
But... why?
If we think passing directories to slicec is okay and meaningful, I don't see a good reason to restrict it to only reference files.
The Slice compiler accepts 2 "kinds" of input files:
sourcefiles: for which we will actually generate codereferencefiles: which we parse, but are only to be referenced bysourcefiles.There is an asymmetry between these two that I'm not sure makes any sense to have.
Source files can only be passed in as individual files, while reference files can be passed as individual files, but also can be passed in by directory. In which case, we scan the directory for any
.slicefiles and use them as references.But... why?
If we think passing directories to slicec is okay and meaningful, I don't see a good reason to restrict it to only reference files.