- 06 May, 2005 3 commits
- 05 May, 2005 3 commits
- 04 May, 2005 4 commits
- 03 May, 2005 1 commit
-
-
simonpj authored
Add a test for multiple local bindings with TH
-
- 02 May, 2005 1 commit
-
-
simonpj authored
Add newtype stupid-theta test
-
- 29 Apr, 2005 1 commit
-
-
simonpj authored
Add kind-error test
-
- 28 Apr, 2005 1 commit
-
-
simonmar authored
Add test for recent fix to overlapping module check
-
- 25 Apr, 2005 1 commit
-
-
simonmar authored
add foreign import '&' test
-
- 22 Apr, 2005 3 commits
- 19 Apr, 2005 1 commit
-
-
simonmar authored
FFI/threaded test
-
- 16 Apr, 2005 1 commit
-
-
ross authored
add another ShouldFail test, and also hook in arrow1 (still a failure, because the error message is poor).
-
- 15 Apr, 2005 2 commits
- 14 Apr, 2005 1 commit
-
-
simonpj authored
(==) and (>=) must be in scope for pattern matching now
-
- 13 Apr, 2005 1 commit
-
-
simonmar authored
accept output
-
- 06 Apr, 2005 1 commit
-
-
simonmar authored
hDuplicateTo test
-
- 05 Apr, 2005 2 commits
- 04 Apr, 2005 3 commits
- 21 Mar, 2005 3 commits
- 18 Mar, 2005 1 commit
-
-
simonpj authored
Make the SOURCE-import programs work right
-
- 17 Mar, 2005 1 commit
-
-
simonmar authored
Add test for +RTS -xc
-
- 15 Mar, 2005 3 commits
-
-
simonpj authored
Add new GADT tests
-
simonmar authored
new unicode test, and accept output
-
ross authored
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)
-
- 14 Mar, 2005 2 commits