Falling Skies: Haskell Tooling and Ecosystem Growth
summary
A tool evolves from a week‑long shell script into a GHC plugin that enforces module boundaries, per‑module import style and unique aliases, prevents virtual import cycles, and adds an assertable Haddock coverage check. It runs as a plugin so errors surface in GHC/HLS, uses TOML for config, and currently supports GHC 9.4–9.12. Migration to the GHC API works but is brittle: choosing parser vs typechecker plugin and finding type information is hard, which keeps unengaged industrial users from contributing. Locks down module trees and it works, but maintenance is costly.
AI-written summary · about
chapters (8)
- 0:00Industrial Haskell use
- 1:54Haskell developer groups
- 9:55GHC plugin case study
- 20:24GHC plugin challenges
- 35:07Tooling defaults vs user needs
- 37:41Haskell tooling bright spots
- 41:38Reaching invisible Haskell users
- 52:02Sustainable ecosystem growth
related talks
22mHaskell Tools, Compilers, Libraries and Community Projects
54mHaskell Project Showcase and Community Contributions
47mIndustrial Strength Laziness: What's Next?
03mInterview
01h 11mHaskell in Industry: Expert Panel on Tooling, Teaching & Real-World Use
01h 26mHaskell Language Server
26mghc-specter: a GHC plugin that inspects the GHC state on live
46mPainless software development with Haskell