Cabal developers meeting of the 24/11/2023

Theophile Hécate Choutri hecate at
Thu Nov 23 23:47:37 UTC 2023

## Current affairs

- Andrea: The issue with GHC 9.6, -fplugin and cabal register seems to be
affecting many users, including stack and rules_haskell:
We had an issue ( opened last
month and we merged a fix (
about three weeks ago. I am not expecting the release gods to get their
hands dirty again but could we make a minor release for this patch?
  - Hécate: No problem for a patch release, we need to ship anyway

- Hécate: No plan for patch releases for 3.8 and 3.6.

- Andrea: [#9374]( (Guard
PackageInfo behind cabal-version: 3.10) we need to make a decision about
what to do. Further discussion is at

  - Mikołaj has a plan:
- Javier: (`default-constraints`
proposal): I'd like to have a first discussion on whether the proposal is
considered beneficial or not, and discuss alternatives to it.
  - `package-constraints` seems to be a more fitting name
  - An RFC for the design for the PR will be opened

## Review needed

- Andrea: I had opened for a
while, blocked on a CI failure on Windows. Can we get someone with Windows
experience to look at the failure (
  - No clear resolution for this problem at this time
  - Javier can't in fact run the test-suite in Windows on this branch.

- Andrea: on standalone foreign
libs. I am happy to extend the documentation but we need to know what we
want to say.
  - Yvan would be happy to help on that :)

- Yvan:, it's mainly code
refactoring, Andrea pair-programmed with me on this one.

- Yvan: Stuck with a bug on,
it's a low-hanging fruit to improve `cabal-install` output.
  - Hécate: Looks like it's a matter of changing hashes?

  - Yvan: Not only

- Rodrigo: Almost done with
reworks a bit --enable-coverage and "re-fixes" #5213, #4798 and will fix

- Rodrigo: Did this fix on a whim I think this happens once in
a while and I've put forward a pragmatic fix. I don't understand what other
situation can trigger this error.

## Food for thoughts

- Andrea: I have played a bit with the lexer to add tokens for whitespace
and comments (maybe a humble step towards exact-printing but I won't make
such a claim). While doing that I noticed the token `TokFieldLine` never
gets emitted by the lexer (I tested this on the whole Hackage). I am not
very well versed in this, does anybody have a clue?
  - Hécate: It might actually be impossible for the Lexer to emit this
token, due to overlap with other things.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the cabal-devel mailing list