Idris2/tests/chez/chez031/run

rm -rf build

$1 --no-banner --no-color --console-width 0 --cg chez Specifiers.idr --exec main
$1 --no-banner --no-color --console-width 0 --cg chez Specifiers.idr -o build/foo
$1 --no-banner --no-color --console-width 0 --cg chez < input
Move rm -rf to the beginning of the test While the discussion about how to refactor test framework is not finished (#1654), make this change: move `rm -rf build` in the beginning of the test. For these reasons: * it is useful to inspect the contents of the `build` directory especially after the test failure * if build crashes mid-test (e.g. process killed), next run should not be affected by the `build` directory from the previous run 2021-07-14 00:54:53 +03:00			`rm -rf build`

add ability to target scheme flavor in foreign specifiers There's some missing flexibility in how foreign specifiers can be used with scheme that is addressed here with minimal changes to how scheme specifiers are read. This opens up uses for users that they otherwise would have had to modify the compiler's support files to accomplish. 2020-09-11 09:51:48 +03:00			`$1 --no-banner --no-color --console-width 0 --cg chez Specifiers.idr --exec main`
add specifier check for cli compilation Missed a case which is covered now by checking for exceptions where postOptions is used add > < to Core 2020-09-14 00:20:50 +03:00			`$1 --no-banner --no-color --console-width 0 --cg chez Specifiers.idr -o build/foo`
add nicer errors for bad specifiers 2020-09-13 01:51:01 +03:00			`$1 --no-banner --no-color --console-width 0 --cg chez < input`
add ability to target scheme flavor in foreign specifiers There's some missing flexibility in how foreign specifiers can be used with scheme that is addressed here with minimal changes to how scheme specifiers are read. This opens up uses for users that they otherwise would have had to modify the compiler's support files to accomplish. 2020-09-11 09:51:48 +03:00