HVR ری ٹویٹ کیا
HVR
527 posts



@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
#cfg-field-reject-unconstrained-dependencies" target="_blank" rel="nofollow noopener">cabal.readthedocs.io/en/latest/caba…
English

@hvrgnu @A64mQ Very nice! I've replaced Stack with Cabal month or so ago and so far it's smooth.
I'd like to add that you can reuse Stackage snapshots with Cabal, to get best of both worlds.
Just pick this file: stackage.org/lts-15.14/caba… and save as cabal.project.freeze!
Works for any LTS.
English

Great article by Luke Lau showing off some of #Haskell #cabal 3.2's useful features for everyday work!
lukelau.me/haskell/posts/…
English

@Adaizen_com @shawn_mcmurdo Are you aware of downloads.haskell.org/debian/ ? It doesn't get easier and more idiomatic than that on Debian IMO.
English

@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.
#t:ProtocolOp" target="_blank" rel="nofollow noopener">hackage.haskell.org/package/LDAPv3…
this trades some verbosity for less cognitive overhead ftw! :-)
English

@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? ;-)
hackage.haskell.org/package/hackag…
English

@a_cowley @cafe2code I was able to build hackage-security-0.6.0.0 with ghc8.10.1 and Cabal 3.2.0.0/cabal-install 3.2 with two additional changes set flag48 to True and remove upper bound on base
English

@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
English

@mightybyte @jkachmar There are two scenarios, both requiring revisions, in the case of a dep major version bump.
No bounds: small chance that it breaks my library, and I need to revise affected versions
Yes bounds: 100% chance that it breaks the build plan, and I need to revise affected versions
English

@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 github.com/haskell/cabal/… and tell us `cabal --version` as well as the output of `dpkg -l 'cabal-install-*'` !
English

@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 qfpl.io/posts/multiple…
English

@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 downloads.haskell.org/debian/ for more details!
English

I am happy to report that the mix-up with the GHC 8.8.1 release artifacts has been resolved. Grab them while they're hot at downloads.haskell.org/ghc/8.8.3/. Happy Haskelling!
English

GHC 8.8.3 is now available! A few nice bug fixes in there so upgrading is encouraged. Thanks to everyone who contributed to this release!
haskell.org/ghc/blog/20200…
English

@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?
English

@hvrgnu The hash of the release commit is d0bab2e3419e49cdbb1201d4650572b57f33420c.
English

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
osa1.net/posts/2020-01-…
English
HVR ری ٹویٹ کیا

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!
kowainik.github.io/projects/aweso…
English
HVR ری ٹویٹ کیا

Pleased to say that three and a half months later, we have officially switched to using `cabal-install` instead of `stack` at @HasuraHQ! 🎉 github.com/hasura/graphql…
Alexis King@lexi_lambda
I’ve been having a crisis of faith in `stack` recently. The UX for beginners is still way better than `cabal-install`, but recent changes have burned me… the removal of `stack solver` sucks, `stack exec` is broken with no workaround, and as of 2.x you can’t uninstall packages!
English
HVR ری ٹویٹ کیا

🆕 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.
vrom911.github.io/blog/common-st…
English

@FlavioCorpa @github @rob_rix @importantshock Well... I *did* such a PR long ago already... but for some reason it wasn't merged back then... :-(
github.com/actions/cache/…
English

Today I contributed the #Haskell - Cabal cache config to @github actions! Although actually I just hijacked @rob_rix and @importantshock's configuration, someone had to do it! 🤷🏼♂️😂 github.com/actions/cache/…
English


