!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

755 Members
For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://haskell4nix.readthedocs.io/ | More Nix: #community:nixos.org | More Haskell: #haskell-space:matrix.org150 Servers

Load older messages


SenderMessageTime
5 Jun 2021
@maralorn:maralorn.demaralorn * maralorn sets the topic to: „Welcome to the Nix & Haskell channel. Days since someone demanded static typing in Nix: 0"17:09:37
@fgaz:matrix.orgfgaz
In reply to @sternenseemann:systemli.org
it does not
Whatt‽ isn't that the opposite of basically every ml-style language?
17:25:35
@fgaz:matrix.orgfgazI always assumed it shadowed17:25:46
@maralorn:maralorn.demaralorn fgaz: There is an issue about that and Eelcos reasoning why it does that is actually quite convincing. 17:26:26
@sternenseemann:systemli.orgsterni (he/him)the correct answer is ofc that with was a bad idea in the first place ;)17:26:53
@maralorn:maralorn.demaralornI think the main advantage of with not shadowing is, that you can never break code by introducing a new value into the withed attrset.17:27:25
@fgaz:matrix.orgfgaz
In reply to @maralorn:maralorn.de
fgaz: There is an issue about that and Eelcos reasoning why it does that is actually quite convincing.
Do you have a link?
17:28:14
@maralorn:maralorn.demaralornSadly I don‘t and with is a terrible word to look for in an issues tracker.17:29:22
@maralorn:maralorn.demaralornwow. Nix has 100 open issues assigned to peti.^^17:30:18
@maralorn:maralorn.demaralorn(ofc I am wildely exagerating it’s actually only 98.)17:30:46
@Las:matrix.orgLas
In reply to @sternenseemann:systemli.org
aeson should already be compiled I'm pretty sure
nix build github:NixOS/nixpkgs?rev=7191381b24b511017207205e2c8625a91ccea5cf#legacyPackages.aarch64-linux.haskell.packages.ghc901.aeson builds it locally for me
20:02:59
@Las:matrix.orgLasIt's this commit: https://github.com/NixOS/nixpkgs/commit/7191381b24b511017207205e2c8625a91ccea5cf20:03:21
@maralorn:maralorn.demaralorn Las: Hm, okay. sterni (he/him) the problem is: We don‘t have a ghc9 cabal2nix job. So we have nothing with a distribution-nixpkgs dependency. 20:07:52
@maralorn:maralorn.demaralornI guess we could/should introduce that job anyways?20:09:34
@maralorn:maralorn.demaralornWe could actually consider building either mergeable or even maintained for ghc9 …20:10:07
@maralorn:maralorn.demaralornI think it’s a bit ridiculous that not even hoogle builds on ghc 9 …20:11:11
@roosemberth:orbstheorem.chRoosI find very disturbing there's so much breakage when the compiler updates...20:18:59
@roosemberth:orbstheorem.chRoos * I find very disturbing for the language there's so much breakage when the compiler updates...20:18:59
* @roosemberth:orbstheorem.chRoos goes to check GHC9 release notes.20:19:00
@maralorn:maralorn.demaralorn Roos: There actually isn‘t much breakage. It’s mostly that a) everyone needs to bump their base upper bound and b) things that link against ghc have a hard time. 20:39:08
@roosemberth:orbstheorem.chRoosThat's reassuring ^^"20:40:13
@fgaz:matrix.orgfgazregarding the discussion from earlier today: I think the haskell binary cache from nixpkgs is mostly useful for experiments or short-term stuff. Once you start working on long-lived project, the warm-up time for the cabal cache gets negligible, and you gain the advantage of being able to work with any version of a package21:07:07
@fgaz:matrix.orgfgaz(of course the haskell stuff in nixpkgs is still very useful for packaging though)21:07:28
@fgaz:matrix.orgfgazIn fact, I almost stopped using nixpkgs for haskell development. Still, nix remains useful for caching this environment for ci, deployments, and sharing it with other developers. And that's why I'm working on my own builder based on cabal and FODs21:11:31
@fgaz:matrix.orgfgaz * regarding the discussion from earlier today: I think the haskell binary cache from nixpkgs is mostly useful for experiments or short-term stuff. Once you start working on long-lived project, the warm-up time for the cabal cache gets negligible, and by avoiding nixpkgs you gain the advantage of being able to work with any version of a package21:12:18
@fgaz:matrix.orgfgaz * regarding the discussion from earlier today: I think the haskell binary cache from nixpkgs is mostly useful for experiments or short-term stuff. Once you start working on long-lived projects, the warm-up time for the cabal cache gets negligible, and by avoiding nixpkgs you gain the advantage of being able to work with any version of a package21:14:48
@maralorn:maralorn.demaralornFOD?21:16:17
@fgaz:matrix.orgfgazFixed-output derivation21:16:57
@maralorn:maralorn.demaralornAh21:17:06
@Las:matrix.orgLaswhat would you use fixed-output derivations for?21:17:34

Show newer messages


Back to Room ListRoom Version: 6