Skip to content

Changing hs-boot doesn't trigger a consistency check

Ticket extracted from #24776 (closed).

  1. Create

A.hs-boot

module A where

A.hs

module A where
  1. Compile ghc A. It succeeds.
  2. Add data T to A.hs-boot only.
  3. Compile ghc A. This unexpectedly succeeds: it recompiles A.hs-boot, but does not check that A.hs is consistent with the boot file.
  4. If you remove A.hi or use -fforce-recomp, then ghc A fails, as expected.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information