cabal haddock can fail if the build artifacts were deleted
Open
Cabal: cmd/haddock
status: consider closing
type: bug
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
Suppose you run `cabal build` on a project, and then later on the build folder gets deleted and you run `cabal haddock`. This will cause a build failure because the `reusingGHCCompilationArtifacts` function expects the artifacts to be there. If instead we simply don't try to copy artifacts that don't exist, haddocking succeeds.
I am fixing in #10992.
Contributor guide
Assessment
This issue has not been assessed yet.