Andreas Abel

Indeed, looks like #6006. The new thing is that even a plain `cabal haddock` fails, since it includes `--enable-documentation` by default now.

Could we have a flag `--ingore-assertions` to force `cabal` to continue?

> This is in a dev build with assertions enabled, right? Not 3.8RC1? Yes, it is 3.9.0.0.

> Fail to repro with the current `master` ([dd312ec](https://github.com/haskell/cabal/commit/dd312ecc44b79945061a4cb45e15b90f26382be4)). @ulysses4ever : I can reproduce this with latest `master` and also GHC 9.2.4. Did you unzip my project and tried it...

I think I was mistaken, content of conditionals _can_ be revised. However, conditionals cannot be _added or deleted_. The OP looks like this: ``` base (>=4 && =1.1) if impl(ghc)...

A simpler example: To allow `bytestring-0.11` just for `GHC >= 8`, I wanted to add to existing `bytestring` bounds the conditional bound ``` if !impl(ghc >=8.0) { build-depends: bytestring <...

> A good first cut would then be that new conditionals can be added iff they only place constraints on dependencies already listed at the top level, Agreed. This should...

Great analysis, @phadej! > ```shell > touch foo.c > ghc -optP -traditional -v3 -c -o foo.o foo.c > # or/and > ghc -pgmP cpp-11 -optP -traditional -v3 -c -o foo.o...

> I'd suggest @andreasabel to open GHC issue about this. I found an upstream issue that looks related enough: https://gitlab.haskell.org/ghc/ghc/-/issues/17185 Here is a relevant comment from the discussion there (by...

> Perhaps some more recent versions should be included on AppVeyor? I suppose so, but I have never used AppVeyor. I think it could be tried to extend the AppVeyor...