@maksbotan@A64mQ btw, if you use workflows that demand closed-world build-plans (and don't achieve that via file+index:// repos), a useful feature not mentioned by the article you might find useful is
https://t.co/EiDbRq2Kri
@pitopos Fwiw, even though this is yet another thing hlint's defaults keep hatin' my source for, I'm quite happy using U+0027 as prefix-separator in my record fields and constructor names, as in e.g.
https://t.co/VOgUz0cGs0
this trades some verbosity for less cognitive overhead ftw! :-)
@to_haskell@a_cowley@cafe2code ...ok, but why insist on forcing a provably incompatible version instead of using version 0.6.0.1 of hackage-security that contains fixups to be *actually* compatible with GHC 8.10's TH API? ;-)
https://t.co/qpITvroISP
#Haskell (ghc-8.10.1) / #Cabal 3.2 / #Xmonad 0.15 Tip of the day:
cabal install -z --lib --package-env=$HOME/.xmonad/ --allow-newer=setlocale-1.0.0.9:base xmonad xmonad-contrib
This will create a CWD-style GHC pkg-env file which will be picked up by `xmonad --recompile` &al.
@mattoflambda@mightybyte@jkachmar This has been debunked many times so just to remind: The problem is that even small chances of failures add-up and propagate through the dep-graph harming/annoying everyone & the longer a semantically unsound buildplan is allowed to circulate, the more costly it becomes to repair
@purelyagile @IvanPerezKeera @MagpieMcGraw All but the "cabal-install-head" package are supposed to be stable releases (or stable release candidates); if you've run into problems please file a report over at https://t.co/8gGZTZu4zA and tell us `cabal --version` as well as the output of `dpkg -l 'cabal-install-*'` !
@IvanPerezKeera @NathanLander Sure, make sure /opt/ghc/bin is in your path, then you can use a `-w ghc-7.8.4` CLI flag on the fly to quickly switch between ghc versions or put
packages: .
with-compiler: ghc-7.8.4
into your per-project `cabal.project` configuration file;
see also https://t.co/cS1O9nbKMx
@bgamari I'd like to plug a friendly reminder that you can get convenient .deb packages for brand new #Haskell GHC 8.8.3 and Cabal 3.2 releases built appositely for your specific #Debian and #Ubuntu releases from our Apt repositories; see https://t.co/rQ6MxayFdb for more details!
@bgamari I'd like to plug a friendly reminder that you can get convenient .deb packages for brand new #Haskell GHC 8.8.3 and Cabal 3.2 releases built appositely for your specific #Debian and #Ubuntu releases from our Apt repositories; see https://t.co/rQ6MxayFdb for more details!
@bgamari ...but are you *really* sure that you built the GHCHQ src+bindist tarballs from that very commit hash and not the one that had been sitting on the ghc/8.8 branch tip until a couple minutes ago, and that now we either need to move the Git tag or scrap the GHCHQ tarball dists?
IMO @_osa1 makes a good case that the overall cost&issues of adding seemingly neat syntax variations to the language extends far beyond an innocent looking 10-line patch (whose OP might not even be involved w #haskell anymore) and isn't taken srsly enough
https://t.co/Q45HKFx98P
We've put together an Awesome list of resources for the #Haskell Cabal build tool 💫 Discover incredible tools and helpful guides all in one place!
And help us to make it even more awesome💅 Share your amazing work if it's anyhow related to Cabal!
https://t.co/Yze7TS3UNN
Pleased to say that three and a half months later, we have officially switched to using `cabal-install` instead of `stack` at @HasuraHQ! 🎉 https://t.co/6ZZJkfblvc
🆕 Blog post time!
I wrote about a nice feature for your #Haskell package configurations — "Common Stanzas". Step by step integration showcase and alternative examples (featuring #Dhall) are included.
https://t.co/1lZh7gHv0x