hi, here is another module system bug: module A where data A = A { t :: Int } module B where import A data B = B { t :: Char } Hugs complains that the selector "t" is already defined. This is wrong, since this error should only be reported if the selector is used ambiguously (e.g. with an unqualified name). bye iavor -- ================================================== | Iavor S. Diatchki, Ph.D. student | | Department of Computer Science and Engineering | | School of OGI at OHSU | | http://www.cse.ogi.edu/~diatchki | ==================================================
Thanks, fixed (but a conflict is of course still reported if it clashes with a local name, irrespective of use.) --sigbjorn ----- Original Message ----- From: "Iavor S. Diatchki" <diatchki@cse.ogi.edu> To: "hugs-bugs" <hugs-bugs@haskell.org> Sent: Thursday, February 13, 2003 15:18 Subject: another module system bug
hi,
here is another module system bug:
module A where data A = A { t :: Int }
module B where import A data B = B { t :: Char }
Hugs complains that the selector "t" is already defined. This is wrong, since this error should only be reported if the selector is used ambiguously (e.g. with an unqualified name).
bye iavor
participants (2)
-
Iavor S. Diatchki -
Sigbjorn Finne