Idris2-boot/tests/ttimp/dot001/run

echo ':q' | $1 --yaffle Dot.yaff
echo ':q' | $1 --yaffle Dot2.yaff
echo ':q' | $1 --yaffle Dot3.yaff
echo ':q' | $1 --yaffle Dot4.yaff

rm -rf build
Change main program to be Idris2 With the --yaffle flag, you get the old behaviour which is to invoke the checker for the core theory (and all the tests are updated appropriately for this). 2019-06-09 13:58:29 +03:00			`echo ':q' \| $1 --yaffle Dot.yaff`
			`echo ':q' \| $1 --yaffle Dot2.yaff`
			`echo ':q' \| $1 --yaffle Dot3.yaff`
			`echo ':q' \| $1 --yaffle Dot4.yaff`
Implement dot patterns Like Idris 1, these are implicitly added on encountering a repeated name or a non-constructor application. Unlike Idris 1 (and Blodwen) they are checking by unification rather than matching (which means in particular that function argument names can't be bound in dot patterns) which is slightly less expressive, but better overall because matching is potentially more error prone. 2019-05-25 20:39:21 +03:00
			`rm -rf build`