#8233: Type environment when reporting holes -------------------------------------------------+------------------------- Reporter: monoidal | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler (Type checker) | Version: 7.7 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Incorrect warning at | Unknown/Multiple compile-time | Difficulty: Test Case: | Unknown Blocking: | Blocked By: | Related Tickets: #8191 -------------------------------------------------+------------------------- Comment (by kosmikus): Oh, given this report, it certainly seems that the "Relevant bindings" are now actually more liberal than I had ever intended. I implicitly assumed that only "local" bindings would ever be shown (i.e., lambda-bound, let- bound and where-bound identifiers defined in the same binding the hole appears in). These are the ones most likely to be relevant, and they're also often tricky / not worthy of giving type signatures for. If we start to include other top-level bindings, I don't know where this would end. For large modules, `TypeHoles` would quickly become useless ... -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/8233#comment:1 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler