Idris2/tests/idris2/reg038/run

rm -rf build

$1 --no-color --console-width 0 Test1.idr --check
$1 --no-color --console-width 0 Test2.idr --check
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`

Correct multiplicities when checking Pi binders We've always just used 0, which isn't correct if the function is going to be used in a runtime pattern match. Now calculate correctly so that we're explicit about which type level variables are used at runtime. This might cause some programs to fail to compile, if they use functions that calculate Pi types. The solution is to make those functions explicitly 0 multiplicity. If that doesn't work, you may have been accidentally trying to use compile-time only data at run time! Fixes #1163 2021-03-09 20:23:05 +03:00			`$1 --no-color --console-width 0 Test1.idr --check`
			`$1 --no-color --console-width 0 Test2.idr --check`