Native executables and the language server
Release v0.4.0
una build [path]checks the package at tier 1, then writes a native executable totarget/una/<name>(spec/16), or to--out <file>. It refuses a package with errors, asuna rundoes;--jsonprintsuna.build/1.- The executable runs
mainof the entry module with the output, failures, exit codes and grants ofuna run: the[run] grantsofuna.tomlare built in, and--grant,--max-depthand--max-memorywork as foruna run. Its--trace <file>writes the trace as a JSON array, the trace thatuna --json runreports inuna.run/1. That its output and trace match the interpreter's is tested, not proven: the toolchain's tests run the runnable programs in both engines and compare them. With tasks on the real clock the order of the effects of different tasks may differ;--virtual-timemakes the executable follow the interpreter's schedule (spec/27 §8 rules 3 and 4). - Tasks of
togetherrun on--workersthreads, one per core by default, in a native executable, and one at a time inuna run. una lspis a language server (LSP 3.17 over stdin and stdout) for editors: it checks as you type, proves a file when it is opened or saved, formats on request, and never runs programs.