<div dir="ltr">## Current affairs<br><br><div>- Andrea: The issue with GHC 9.6, -fplugin and cabal register seems to be affecting many users, including stack and rules_haskell: <a href="https://discourse.haskell.org/t/ghcs-fplugin-any-changes-between-9-4-7-and-9-6-2/7656/4">https://discourse.haskell.org/t/ghcs-fplugin-any-changes-between-9-4-7-and-9-6-2/7656/4</a>. </div><div>We had an issue (<a href="https://github.com/haskell/cabal/issues/9375">https://github.com/haskell/cabal/issues/9375</a>) opened last month and we merged a fix (<a href="https://github.com/haskell/cabal/pull/9384">https://github.com/haskell/cabal/pull/9384</a>) 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?</div>  - Hécate: No problem for a 3.10.3.0 patch release, we need to ship <a href="https://github.com/haskell/cabal/pull/9459">https://github.com/haskell/cabal/pull/9459</a> anyway<br><br><div>- Hécate: No plan for patch releases for 3.8 and 3.6. <br></div><div><br></div><div>- Andrea: [#9374](<a href="https://github.com/haskell/cabal/pull/9374">https://github.com/haskell/cabal/pull/9374</a>) (Guard PackageInfo behind cabal-version: 3.10) we need to make a decision about what to do. Further discussion is at <a href="https://github.com/haskell/cabal/issues/9331">https://github.com/haskell/cabal/issues/9331</a>.</div><div><br></div>  - Mikołaj has a plan: <a href="https://github.com/haskell/cabal/issues/9331#issuecomment-1792219043">https://github.com/haskell/cabal/issues/9331#issuecomment-1792219043</a><br>- Javier: <a href="https://github.com/haskell/cabal/pull/9462">https://github.com/haskell/cabal/pull/9462</a> (`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.<br>  - `package-constraints` seems to be a more fitting name<br>  - An RFC for the design for the PR will be opened<br><br>## Review needed<br><br>- Andrea: I had <a href="https://github.com/haskell/cabal/pull/9123">https://github.com/haskell/cabal/pull/9123</a> opened for a while, blocked on a CI failure on Windows. Can we get someone with Windows experience to look at the failure (<a href="https://github.com/haskell/cabal/actions/runs/6480591351/job/17596418675#step:18:1663">https://github.com/haskell/cabal/actions/runs/6480591351/job/17596418675#step:18:1663</a>)?<br>  - No clear resolution for this problem at this time<br><div>  - Javier can't in fact run the test-suite in Windows on this branch.</div><div><br></div>- Andrea: <a href="https://github.com/haskell/cabal/pull/9320">https://github.com/haskell/cabal/pull/9320</a> on standalone foreign libs. I am happy to extend the documentation but we need to know what we want to say.<br>  - Yvan would be happy to help on that :)<br><br><div>- Yvan: <a href="https://github.com/haskell/cabal/pull/9159">https://github.com/haskell/cabal/pull/9159</a>, it's mainly code refactoring, Andrea pair-programmed with me on this one.</div><div><br></div>- Yvan: Stuck with a bug on <a href="https://github.com/haskell/cabal/pull/9160">https://github.com/haskell/cabal/pull/9160</a>, it's a low-hanging fruit to improve `cabal-install` output.<br><div>  - Hécate: Looks like it's a matter of changing hashes? <a href="https://github.com/haskell/cabal/actions/runs/6783137983/job/18436767543?pr=9160#step:15:18">https://github.com/haskell/cabal/actions/runs/6783137983/job/18436767543?pr=9160#step:15:18</a> </div><div>  - Yvan: Not only <a href="https://github.com/haskell/cabal/pull/9160#issuecomment-1798232254">https://github.com/haskell/cabal/pull/9160#issuecomment-1798232254</a></div><div><br></div><div>- Rodrigo: Almost done with <a href="https://github.com/haskell/cabal/pull/9464">https://github.com/haskell/cabal/pull/9464</a>: reworks a bit --enable-coverage and "re-fixes" #5213, #4798 and will fix #6440.</div><div><br></div>- Rodrigo: Did this fix on a whim <a href="https://github.com/haskell/cabal/issues/9448">https://github.com/haskell/cabal/issues/9448</a>. 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.<br><br>## Food for thoughts<br><br>- 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?<br>  - Hécate: It might actually be impossible for the Lexer to emit this token, due to overlap with other things.</div>