Delete FakeMap.
Compute 'UnitId' when we compute a 'ConfiguredPackage';
consequently, we can eliminate 'FakeMap' (finally!)
There is one hack remaining, which is that 'SolverInstallPlan'
gins up fake unit IDs so that it can be keyed on UnitIds.
But this data structure exists only very briefly before
being converted into an 'InstallPlan' or 'ElaboratedInstallPlan'.
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
Showing
- cabal-install/Distribution/Client/BuildReports/Storage.hs 2 additions, 2 deletionscabal-install/Distribution/Client/BuildReports/Storage.hs
- cabal-install/Distribution/Client/Configure.hs 3 additions, 2 deletionscabal-install/Distribution/Client/Configure.hs
- cabal-install/Distribution/Client/Freeze.hs 6 additions, 3 deletionscabal-install/Distribution/Client/Freeze.hs
- cabal-install/Distribution/Client/Install.hs 16 additions, 28 deletionscabal-install/Distribution/Client/Install.hs
- cabal-install/Distribution/Client/InstallPlan.hs 43 additions, 72 deletionscabal-install/Distribution/Client/InstallPlan.hs
- cabal-install/Distribution/Client/InstallSymlink.hs 5 additions, 5 deletionscabal-install/Distribution/Client/InstallSymlink.hs
- cabal-install/Distribution/Client/PlanIndex.hs 33 additions, 89 deletionscabal-install/Distribution/Client/PlanIndex.hs
- cabal-install/Distribution/Client/ProjectPlanning.hs 1 addition, 1 deletioncabal-install/Distribution/Client/ProjectPlanning.hs
- cabal-install/Distribution/Client/Types.hs 14 additions, 14 deletionscabal-install/Distribution/Client/Types.hs
Loading
Please register or sign in to comment