[GHC] #10411: Neighbour let-bindings are not reported as relevant
GHC
ghc-devs at haskell.org
Sun May 17 08:19:18 UTC 2015
#10411: Neighbour let-bindings are not reported as relevant
-------------------------------------+-------------------------------------
Reporter: Feuerbach | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 7.10.1
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
Type of failure: None/Unknown | Unknown/Multiple
Blocked By: | Test Case:
Related Tickets: | Blocking:
| Differential Revisions:
-------------------------------------+-------------------------------------
Comment (by Feuerbach):
How about including all local bindings that are in scope at that point?
The motivation is:
1. Some of the local bindings will likely be used to fill in the hole
2. There are typically not too many of them, so the output will stay
relevant (as opposed to including global bindings, too)
3. The feature is especially useful for local bindings, since getting
their type requires a bit of extra work (again, as opposed to global
bindings)
I don't have an opinion on whether this should replace or be added to the
current type-based algorithm which you describe (and which I wasn't aware
of until now).
Although if I understand the current algorithm correctly, it will only
ever report bindings from the current declaration (since type variables
cannot be shared across declarations), so in that case my proposal seems
to be about simply lifting the type-based restriction.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10411#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list