[GHC] #10419: Refactor LoadIface to distinguish getting a ModIface versus loading into EPT

[GHC]

#10419: Refactor LoadIface to distinguish getting a ModIface versus loading into
EPT
-------------------------------------+-------------------------------------
        Reporter:  ezyang            |                   Owner:  ezyang
            Type:  task              |                  Status:  closed
        Priority:  normal            |               Milestone:
       Component:  Compiler (Type    |                 Version:  7.11
  checker)                           |                Keywords:
      Resolution:  invalid           |            Architecture:
Operating System:  Unknown/Multiple  |  Unknown/Multiple
 Type of failure:  None/Unknown      |               Test Case:
      Blocked By:                    |                Blocking:
 Related Tickets:                    |  Differential Revisions:
-------------------------------------+-------------------------------------
Changes (by ezyang):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 My original motivation was clarity surrounding plugin interface loading,
 but actually I think there's a better way to solve this problem (#10420),
 so I guess let's let this die.

 Though, I think it may still be useful to add a new function to
 `LoadIface` expressly for orphan loading, to consolidate this logic.

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