Closed sternenseemann closed 1 year ago
@mfourne Thanks for the patches. I've rebased this work into my own fork and can confirm this builds ok with ghc-9.4.
Who is maintainer and what's the process for getting stuff merged? What's the support window for ghc versions?
I might have a go a fixing up the many warnings but some of that might not be backward compatible. Should there be ghc version branches here?
@sebeaumont I think that would currently be me - let's work together on that! I'm currently running ghc-9.0 and mostly care for Debian shipped ghc versions, but I'll first try to find out if there is some support window. Could you put your fork into a PR, so we can work on it for upstreaming? From this, we can either make a branch or merge it directly.
@mfourne Sorry for slow response got hit by covid
and new hardware! The latter has been a lot more fun I can confirm that I managed to build and run with ghc-9.4.3
on Mac OS (latest) with M1 (aarch64) toolchain -- lots of warnings which should be easy to fix but might affect backward compatibility I guess. Noticed some weird key behaviour on a cursory OOB test but I'll start looking more deeply now. BTW I tend not to use stack as cabal serves me well for all but big day job mono-rep builds (all x86 plat) and indeed it seems a bit flakey on this platform.
@sebeaumont I just merged my old PR for this, fixing the titular issue. Can you open a new issue for your fixes up to ghc-9.4.3 and attach a PR there? I'm closing this issue, since the issue with GHC 9.0 from Stackage lts-19 should be fixed now, as some testing in Debian has not brought up new issues with my patches there.