ffaf1
ffaf1
> require each commit to reference an issue [We do](https://github.com/haskell/cabal/blob/master/CONTRIBUTING.md#pull-requests--issues) but it is not enforced strictly.
Hello, I am going through old PRs to check whether they are stale. If this PR is still “live”, write a comment and I will remove the `consider closing` label....
Reasonable UX request
It most likely is [!23762](https://gitlab.haskell.org/ghc/ghc/-/issues/23762). Note that your CI on 9.4.7 is *green*, not red. I wonder: - Why does our CI not break? - If there is anything else...
I see, it makes sense. Let's add `lookupIdSubst` to the discussion, because this is the specific GHC function that panics (included in the error).
Bitten by this today. Inspecting the output of `--list-formats`, I found that the original tracked is described as “original”, hopefully there is a less fragile way to select it.
Since the draft references `v1` commands, I am reading #10262. Does “no one feels confident in making that change without a clearer mandate or process” apply there? It seems to...
@andreasabel , @andreabedini and @grayjay could be interested.
> How hard is it to release just Cabal and Cabal-syntax without the breaking changes as 3.12.2? I don't think it's hard? Definitely not. What about `3.12.1.0` (`Cabal` and `Cabal-syntax`)?...
I will add that we need to decide what to do *now*, too, for `3.12.2.0`. Revert the changes? Leave them there since most likely people have alreaded updated their code?...