"Found hole"
Alex Hammel
ahammel87 at gmail.com
Tue Jan 20 20:39:55 UTC 2015
You can get typed holes to compile with a warning and a runtime error with
the -fdefer-type-errors flag, if that's what you want.
However, it's perfectly legal to use identifiers which look like typed
holes. This works fine on 7.8.3ghc:
_exit = print
main = _exit 0
On Tue, Jan 20, 2015 at 11:25 AM, Alex Hammel <ahammel87 at gmail.com> wrote:
> The only reference to a NoTypedHoles extension google can find is this
> thread. Odd.
>
> On Tue, Jan 20, 2015 at 11:22 AM, Volker Wysk <verteiler at volker-wysk.de>
> wrote:
>
>> Hi!
>>
>> Am Dienstag, 20. Januar 2015, 13:44:01 schrieben Sie:
>> > The leading underscore invokes the typed holes extension. If you want to
>> > use such names, you'll need {-# LANGUAGE NoTypedHoles #-} as the first
>> line
>> > of the source file.
>>
>> I get this error, when I use "{-# LANGUAGE NoTypedHoles #-}":
>>
>> ex.hs:1:14: Unsupported extension: NoTypedHoles
>>
>> I'm using GHC 7.8.3. Could it be that the "NoTypedHoles" extension was
>> added
>> not before 7.8.4 (the most current version).
>>
>> Bye
>> Volker
>> _______________________________________________
>> Glasgow-haskell-users mailing list
>> Glasgow-haskell-users at haskell.org
>> http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/glasgow-haskell-users/attachments/20150120/297ace3e/attachment.html>
More information about the Glasgow-haskell-users
mailing list