GHC.Unit.External · ghc-10.0.0.20260917

newtypenewtype ExternalUnitCache

Information about the currently loaded external packages. This is mutable because packages will be demand-loaded during a compilation run as required.

Constructors

ExternalUnitCache
- euc_eps :: IORef ExternalPackageState

valueinitExternalUnitCache :: IO ExternalUnitCache

#

valueeucEPS :: ExternalUnitCache -> IO ExternalPackageState

#

datadata ExternalPackageState

#

Information about other packages that we have slurped in by reading their interface files

Constructors

EPS
- eps_is_boot :: !InstalledModuleEnv ModuleNameWithIsBoot
  In OneShot mode (only), home-package modules accumulate in the external package state, and are sucked in lazily. For these home-pkg modules (only) we need to record which are boot modules. We set this field after loading all the explicitly-imported interfaces, but before doing anything else
  The ModuleName part is not necessary, but it's useful for debug prints, and it's convenient because this field comes direct from GHC.Tc.Utils.imp_dep_mods
- eps_PIT :: !PackageIfaceTable
  The ModIfaces for modules in external packages whose interfaces we have opened. The declarations in these interface files are held in the eps_decls, eps_inst_env, eps_fam_inst_env and eps_rules fields of this record, not in the mi_decls fields of the interface we have sucked in.
  What is in the PIT is:
  - The Module
  - Fingerprint info
  - Its exports
  - Fixities
  - Deprecations and warnings
- eps_free_holes :: InstalledModuleEnv (UniqDSet ModuleName)
  Cache for mi_free_holes. Ordinarily, we can rely on the eps_PIT for this information, EXCEPT that when we do dependency analysis, we need to look at the Dependencies of our imports to determine what their precise free holes are (moduleFreeHolesPrecise). We don't want to repeatedly reread in the interface for every import, so cache it here. When the PIT gets filled in we can drop these entries.
- eps_PTE :: !PackageTypeEnv
  Result of typechecking all the external package interface files we have sucked in. The domain of the mapping is external-package modules
- eps_iface_bytecode :: !ModuleEnv (IO Linkable)
  If an interface was written with -fwrite-if-simplified-core, this will contain an IO action that compiles bytecode from core bindings.
  See Note [Interface Files with Core Definitions]
- eps_inst_env :: !PackageInstEnv
  The total InstEnv accumulated from all the external-package modules
- eps_fam_inst_env :: !PackageFamInstEnv
  The total FamInstEnv accumulated from all the external-package modules
- eps_rule_base :: !PackageRuleBase
  The total RuleEnv accumulated from all the external-package modules
- eps_ann_env :: !PackageAnnEnv
  The total AnnEnv accumulated from all the external-package modules
- eps_complete_matches :: !PackageCompleteMatches
  The total CompleteMatches accumulated from all the external-package modules
- eps_mod_fam_inst_env :: !ModuleEnv FamInstEnv
  The family instances accumulated from external packages, keyed off the module that declared them
- eps_stats :: !EpsStats
  Statistics about what was loaded from external packages
- eps_defaults :: !ModuleEnv DefaultEnv
  Default declarations exported by external packages

valueinitExternalPackageState :: ExternalPackageState

#

datadata EpsStats

#

Accumulated statistics about what we are putting into the ExternalPackageState. "In" means stuff that is just read from interface files, "Out" means actually sucked in and type-checked