!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

690 Members
For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://nixos.org/manual/nixpkgs/unstable/#haskell | Current PR: https://github.com/nixos/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Ahaskell-updates | Maintainer Docs: https://github.com/NixOS/nixpkgs/blob/haskell-updates/pkgs/development/haskell-modules/HACKING.md | More Nix: #community:nixos.org | More Haskell: #haskell-space:matrix.org | Merger Schedule: https://cloud.maralorn.de/apps/calendar/p/H6migHmKX7xHoTFa/dayGridMonth/now | Join #haskell.nix:libera.chat for question about the alternative haskell.nix infrastructure137 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
5 Sep 2025
@maralorn:maralorn.demaralornI feel like I am overlooking something because that didn’t feel as painful before …12:18:04
@artem.types:matrix.orgArtem maralorn: the very strict bounds that Ormolu puts on Cabal-syntax look strange. I'd ask on their bug tracker exactly the question you're posing above: if you use ghc-lib-parser, you probably want to span over at least couple of GHC, but you also always limit Cabal-syntax to one version, so this looks like mixed messages... They always bump Cabal-syntax when they bump ghc-lib-parser, so they at least understand some connection they just overly pessimistic about it it looks like. 15:10:21
@maralorn:maralorn.demaralornI guess using ghc-lib-parser might have other advantages than just the compatibility range …15:14:22

Show newer messages


Back to Room ListRoom Version: 6