Making GHCi compatible with multiple home units
summary
GHCi now treats multiple home units as the default: it introduces an interactive GHCI home unit that depends on all loaded components and an interactive session home unit for scripts, so reloads propagate across packages and GHCI commands like :browse/:set/:info and the debugger work across unit boundaries (debugger patched with Rodrigo Mesquita’s changes). The implementation is merged on GHC head and currently requires Cabal’s enable-multirepl flag; future work aims to make multi-unit sessions the unconditional default.
AI-written summary · about
chapters (7)
- 0:00Multiple home units in GHCi
- 2:37GHCi limitations with multiple units
- 4:23Interactive home unit
- 7:56Scripts with interactive unit
- 13:17Live demo of new features
- 16:47Future work and challenges
- 19:17Summary
related talks
22mA look across the pond: a comparison between GHC and Racket compilation models
01h 22mGetting Up and Running, and Contributing to GHC
06mLightning Talk Slot #4: Modularizing GHC
01h 30mGHC Proposal Presentations
33mLightning Talks II
01h 37mGHC's Renamer
25mCompiling Mu with GHC: Halfway Down the Rabbit Hole
26mHot Call-Chain Inlining for the Glasgow Haskell Compiler