T3330a: wrong stderr output (new type checking algorithm?)

T3330a failed with

Actual stderr output differs from expected:
--- ./indexed-types/should_fail/T3330a.stderr.normalised	2011-04-02 19:06:10.000000000 +0200
+++ ./indexed-types/should_fail/T3330a.comp.stderr.normalised	2011-04-02 19:06:10.000000000 +0200
@@ -1,11 +1,9 @@

-T3330a.hs:17:44:
-    Couldn't match type `ix' with `r0 ix0 -> Writer [AnyF s0] (r0 ix0)'
-      `ix' is a rigid type variable bound by
+T3330a.hs:17:34:
+    Couldn't match type `s' with `(->) (s ix1 -> ix1)'
+      `s' is a rigid type variable bound by
            the type signature for children :: s ix -> PF s r ix -> [AnyF s]
            at T3330a.hs:17:1
-    Expected type: PF s r (r0 ix0 -> Writer [AnyF s0] (r0 ix0))
-      Actual type: PF s r ix
-    In the third argument of `hmapM', namely `x'
+    In the first argument of `hmapM', namely `p'
     In the first argument of `execWriter', namely `(hmapM p collect x)'
     In the expression: execWriter (hmapM p collect x)
*** unexpected failure for T3330a(normal)

could be due to the new type checking algorithm.

Trac metadata

Trac field	Value
Version	7.0.3
Type	Bug
TypeOfFailure	OtherFailure
Priority	normal
Resolution	Unresolved
Component	Test Suite
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture