On Sun, Apr 18, 2021 at 01:31:08PM +0200, Bertram Felgenhauer via Haskell-Cafe wrote:
In principle, most of SafeHaskell's functionality could be covered by external tools, including managing lists of safe/trusted/unsafe modules (or exports) and tracking safety dependencies for inferred safety or unsafety. [...] [*] I'm a bit worried that I'm being too naive there. Why is SafeHaskell such a burden within GHC? Is it because it touches many parts, from language pragmas to interface files to actually checking imports? Or am I forgetting something about SafeHaskell that requires deep integration, say, into the type checker?
To this point, I think it's worth noting what aspect of SafeHaskell is difficult to maintain in GHC yet would be easy to maintain outside of GHC, if anything.