Currently the compilation goes from some sources into purs -g corefn -o <output-dir>, which will spit them into <output-dir>. We then iterate over the corefn.json files found in <output-dir>, but those files give no hint back to where they originated from, making it necessary to remember their origin somehow.
Currently the compilation goes from some sources into
purs -g corefn -o <output-dir>
, which will spit them into<output-dir>
. We then iterate over the corefn.json files found in<output-dir>
, but those files give no hint back to where they originated from, making it necessary to remember their origin somehow.