[GHC] #10569: Optionally treat an out-of-scope variable like a typed hole

[GHC]

#10569: Optionally treat an out-of-scope variable like a typed hole
-------------------------------------+-------------------------------------
        Reporter:  simonpj           |                Owner:
            Type:  feature request   |               Status:  new
        Priority:  normal            |            Milestone:  8.0.1
       Component:  Compiler          |              Version:  8.0.1
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by simonpj):

 Well, you could not use `-fdefer-typed-holes`, couldn't you?  After all,
 that too makes your program crash at runtime if you meet a hole.

 It'd be easy enough to put this behaviour behind a flag, say `-fdefer-out-
 of-scope-variables`.  (I think it's quite nice to get the type info for an
 out-of-scope variable.)

 The only downside is yet another flag, user manual entry etc.

 Simon

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10569#comment:8>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler