Oleg Grenrus

Compare ### no LF ```haskell *CabalDocspec.Lexer> traverse_ print $ L.lexerPass0 "1 + 1 -- foo" (IntLit,(Pos {char = 0, line = 1, column = 1},"1")) (Whitespace,(Pos {char = 1, line...

v2-freeze creates freeze file with non-single-point version ranges.

5

**Describe the bug** After `v2-freeze` I see things like ``` any.hashable ==1.2.7.0 || ==1.3.0. ``` in `cabal.project.freeze`. **To Reproduce** I'm able to reproduce this with a current `master` of [`postgresql-simple`](https://github.com/phadej/postgresql-simple)...

Add --ignore-project to v2-build

7

E.g. to prevent looking `cabal.project` somewhere up in the directory tree

haddock flags are not hashed

3

Try (with clean store) ``` cabal haddock --enable-documentation ``` build succeeds. Then ``` cabal haddock --enable-documentation --haddock-for-hackage ``` then fails with e.g. ``` haddock: internal error: /cabal/store/ghc-9.2.5/lattices-2.1-d73b3b45d6e9cfdff466bcdd682b8b68f15a545af43b3b9dea31c352516883bc/share/doc/html/doc-index.json: openBinaryFile: does not...

toUpper and friends are all `INLINE`d

1

So every single call has these functions replicated. Is this intentional? This causes code-bloat for questionable performance benefits (the known call is not *that* slow).

v2-haddock doesn't define __HADDOCK__

1

Defining it will mean rebuilding stuff. But this is regression, AFAICS.

``` % cabal-3.12.1.0 path compiler-flavour: ghc compiler-id: ghc-9.2.8 compiler-path: /opt/ghcup/.ghcup/bin/ghc cache-home: /home/phadej/.cache/cabal remote-repo-cache: /cabal/packages logs-dir: /cabal/logs store-dir: /cabal/store config-file: /cabal/config installdir: /cabal/bin ``` However due https://github.com/haskell/cabal/pull/9326, this information is not...

AFAICT, the `hashable` is used for semi-persistent, low-rate hashing. The `hashable` is not designed for that: ``` localFileNameForRemoteTarball :: URI -> FilePath localFileNameForRemoteTarball uri = mangleName uri ++ "-" ++...