hello, here is another module system bug: module A where data A = K module B where import A data B = K f K = 'k' Hugs should report that the use of "K" in the definition of "f" is ambiguous (as it may refer to the "K" defined in either A or B). Instead, it infers the type "B -> Char" for "f", so it looks like the local constructor shadows the imported one. 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, now fixed.
--sigbjorn
----- Original Message -----
From: "Iavor S. Diatchki"
hello,
here is another module system bug:
module A where data A = K
module B where import A
data B = K
f K = 'k'
Hugs should report that the use of "K" in the definition of "f" is ambiguous (as it may refer to the "K" defined in either A or B). Instead, it infers the type "B -> Char" for "f", so it looks like the local constructor shadows the imported one.
bye iavor
participants (2)
-
Iavor S. Diatchki -
Sigbjorn Finne