| | 117 | * Comment in HscTypes: |
| | 118 | {{{ |
| | 119 | -- If the module does come from the home package, why do we look in the PIT as well? |
| | 120 | -- (a) In OneShot mode, even home-package modules accumulate in the PIT |
| | 121 | -- (b) Even in Batch (--make) mode, there is *one* case where a home-package |
| | 122 | -- module is in the PIT, namely GHC.Prim when compiling the base package. |
| | 123 | -- We could eliminate (b) if we wanted, by making GHC.Prim belong to a package |
| | 124 | -- of its own, but it doesn't seem worth the bother. |
| | 125 | }}} |
| | 126 | We now have a separate {{{ghc-prim}}} package. Should we eliminate (b) then? |