GitLab

Rearrange arrows tests, and move tc120fail to arrowfail003.

add output -- not the best error message, but it's hard to see how
we can do better.

update output ("GHC internal error" wasn't very auspicious)

add another ShouldFail test, and also hook in arrow1 (still a failure,
because the error message is poor).

change to ShouldFail, with a brief explanation.

two recent GHC 6.4 crashes (neither yet fixed)

Fix (and test) for SourceForge bug 1161624: erroneous rejection of

	foo = proc x -> arr (\y -> y-1) -< x

Now open a new level for the left side of -<, so that variables bound
in the proc are illegal, but variables bound in the expression are OK.

Note that the levels gimmick doesn't really implement holes in the
scope: it rules out nasty obfuscations like

	foo x = proc x -> arr (\y -> x-1) -< x

Also added the same treatment to the head of a `form', where it was
missing.

(for STABLE)

mark groups of tests as GHC-only, as they test GHC-specific features.

arrow notation: allow arrow applications (f -< a) to take a non-empty
command stack, as suggested by Sebastian Boldt <Sebastian.Boldt@arcor.de>.

oops, should be on the branch

arrowcase1 is an expected failure on the branch

expand test to include cases of lambdas

update tests to match revised syntax for forms (and test application too).

add a test for big tuples, but don't enable it because it takes a
long time (thanks to the monster types, I suspect).

update arrows test

another arrows test

-farrows instead of -fgla-exts

extend a test

another (successful) arrow test

more arrow tests

update arrow tests

more arrows tests

tests for arrow notation (needs arrows-branch)

Add makefile

Begin arrow test suite