On Mon, Mar 11, 2013 at 9:33 PM, Isaac Dupree
m...@isaac.cedarswampstudios.org wrote:
On 03/11/2013 07:04 PM, Simon Peyton-Jones wrote:
Aha. It is indeed true that
ghc -fdefer-type-errors -w
does not suppress the warnings that arise from the type errors;
indeed there is no current way to
When I ran this code (ghc 7.6.1), I did get the Hello, world! printout. That
line was sandwiched between the compile-time warning from the type error and
the run-time exception from the type error, but the output was there:
09:24:28 ~/temp runghc Scratch.hs
Scratch.hs:5:12: Warning:
No
Hi,
When I ran this code (ghc 7.6.1), I did get the Hello, world!
printout. That line was sandwiched between the compile-time warning
from the type error and the run-time exception from the type error,
but the output was there:
Thank you for letting me know this. I'm also using GHC 7.6.1.
I
Excerpts from Simon Peyton-Jones's message of Mon Mar 11 16:04:31 -0700 2013:
Aha. It is indeed true that
ghc -fdefer-type-errors -w
does not suppress the warnings that arise from the type errors; indeed there
is no current way to do so. How to do that?
To be kosher there should
When I ran this code (ghc 7.6.1), I did get the Hello, world!
printout. That line was sandwiched between the compile-time warning
from the type error and the run-time exception from the type error,
but the output was there:
Thank you for letting me know this. I'm also using GHC 7.6.1.
I
On 03/11/2013 07:04 PM, Simon Peyton-Jones wrote:
Aha. It is indeed true that
ghc -fdefer-type-errors -w
does not suppress the warnings that arise from the type errors;
indeed there is no current way to do so. How to do that?
To be kosher there should really be a flag to switch off
