• Simon Peyton Jones's avatar
    Re-work the naming story for the GHCi prompt (Trac #8649) · 73c08ab1
    Simon Peyton Jones authored
    The basic idea here is simple, and described in Note [The interactive package]
    in HscTypes, which starts thus:
        Note [The interactive package]
        Type and class declarations at the command prompt are treated as if
        they were defined in modules
        with each bunch of declarations using a new module, all sharing a
        common package 'interactive' (see Module.interactivePackageId, and
        This scheme deals well with shadowing.  For example:
           ghci> data T = A
           ghci> data T = B
           ghci> :i A
           data Ghci1.T = A  -- Defined at <interactive>:2:10
        Here we must display info about constructor A, but its type T has been
        shadowed by the second declaration.  But it has a respectable
        qualified name (Ghci1.T), and its source location says where it was
        So the main invariant continues to hold, that in any session an original
        name M.T only refers to oe unique thing.  (In a previous iteration both
        the T's above were called :Interactive.T, albeit with different uniques,
        which gave rise to all sorts of trouble.)
    This scheme deals nicely with the original problem.  It allows us to
    eliminate a couple of grotseque hacks
      - Note [Outputable Orig RdrName] in HscTypes
      - Note [interactive name cache] in IfaceEnv
    (both these comments have gone, because the hacks they describe are no
    longer necessary). I was also able to simplify Outputable.QueryQualifyName,
    so that it takes a Module/OccName as args rather than a Name.
    However, matters are never simple, and this change took me an
    unreasonably long time to get right.  There are some details in
    Note [The interactive package] in HscTypes.
HscMain.hs 65.1 KB