Admin message

Due to a large amount of spam we do not allow new users to create repositories, they are "external" users. If you are a new user and want to create a repository, for example for forking GHC, open a new issue on ghc/ghc using the "get-verified" issue template

Avoiding recompilation when export lists expand
I was reading https://gitlab.haskell.org/ghc/ghc/-/wikis/commentary/compiler/recompilation-avoidance and it says: > for a module that was imported, the export-list fingerprint of the imported module is recorded. If any of the modules we imported now has a different export list we must recompile, so we check the current export-list fingerprints against those recorded in the usages. I'm not sure if GHC is being overly pessimistic here, or if this is actually necessary (maybe something to do with typeclasses?). If a downstream module has an explicit import list, is it necessary to recompile if a new export is added? For instance, a common pattern is to have a `Types.Ids` module that exports a `newtype FooId = FooId Int` for each domain type. This means that whenever a new export is added basically every module recompiles, even though they often have an explicit import list and only use a small subset of these types.
issue