Hello,
Doesn't runghc support the -fdefer-type-errors option?
Consider this code:
module Main where
main :: IO ()
main = do
-- putStrLn は文字列を取る
putStrLn "Hello, world!"
putStrLn 1 -- 型エラー
If I use runghc with -fdefer-type-errors, "Hello, world!" is not
prin
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 ins
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.
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 those warnings alone,
perhaps
-fno-warn-typ
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
| I don’t feel in the position to actually make a call here, or even to cast a
vote with
| confidence, but I’m happy to continue summarizing the discussion until a
| consensus is found. If there is more discussion, that is.
I've updated the page http://hackage.haskell.org/trac/ghc/wiki/SplitBa
On Mon, Mar 11, 2013 at 4:45 PM, Simon Peyton-Jones
wrote:
> B Better for internal implementation (eg using containers or bytestring in
> base)
>
Note that this also means better code for external clients, as we can offer
e.g. a better System.IO that lets people use Handles to read Text and
ByteS
>> 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
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 switc
