Closed zudov closed 8 years ago
Huh, weird. Is this causing a compile error?
Yes. I first noticed it yesterday on psc's HEAD.
line 220, column 5 - line 221, column 5
Type variable m is undefined.
while checking the kind of m0 (FingerTree v0 (Node v0 a0))
while checking the kind of m0 (FingerTree v0 (Node v0 a0))
while checking that expression let
l = (traverse (...)) (force m)
kl = ((<$>) const) l
in ((<*>) ((...) (...))) ((traverse f) sf)
has type m0 (FingerTree v0 b0)
in value declaration traversableFingerTree
See https://github.com/purescript/purescript/wiki/Error-Code-UndefinedTypeVariable for more information,
or to contribute content related to this error.
Makes total sense to me (the m
variable is actually not defined anywhere).
Ah, right, that makes sense. I was just wondering why I hadn't seen it. Thanks!
If they are really necessary (as documentation), we can just add some foralls