On Dec 5, 2007 7:43 AM, Luis Cabellos <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I have a question, what's the best way to program? <br> - put all the signatures in the Haskell Code? <br> - Only put the type signatures needed to compile (like monomorphism errors or ambiguous signature)?
<br>Until now, I prefer the second one, but when I use the -Wall option, there's a lot of complains about type signature. Maybe the type signature is something that not need to be checked as a warning.<br><br>But if the best practice is to put all the signatures, I found that Cabal generated code need to be fixed, because -Wall complains about it also.
<br clear="all"><font color="#888888"><br></font></blockquote><div><br>Hi Luis,<br><br>I don't know what the best way to program is, but I usually put signatures on all functions. I think it often helps get smarter error messages from the compiler. ;-)
<br><br>So I like the warning about missing signatures. If you don't like it you can disable it like this:<br><br><div style="margin-left: 40px;">-Wall -fno-warn-missing-signatures<br></div><br>or maybe use -W instead of -Wall, apparently the warn-missing-signatures is not comprised in the -W flag.