News from the front!
With the completion of one of the oldest tickets in our tracker by Raoul HC, flora-server is gaining the ability to host and serve package archives. We're getting closer to a #Haskell package repository that you will be able to deploy yourself!
Tomorrow is #Haskell Unfolder day! In our 13th episode, Edsko and I will be discussing the topic of "open recursion". Join us live on YouTube 2023-10-25 at 1830 UTC (or watch the recording later):
I created this cheat sheet about #combinators and their #haskell|-equivalents. Since I didn't find something similiar in my learning process, I thought this could be helpful for others
After much failure with trying to get my #haskell#sdl2 project running with #nix, I find the workaround is to use an environmental variable to set SDL_RENDER_DRIVER=software and skip using drivers entirely, I guess?
In #Haskell,
(foldl1' nums) <$> [min, max]
gives [a, b] being the minimum and maximum of nums. Is there a concise way to get a tuple instead without writing fold twice? Seems like something to do with bifunctors or arrows, but I haven't managed to wrap my head around it yet. (I realize this is somewhat pointless golfing)
Got in touch with a company that is looking to hire for Haskell + Elm in Gothenburg, Sweden. Considering how much interest my last static FP job posting drew I figure there might be one or two of y'all in Gbg. Help spread it if you think you know people of interest.
#haskell folk: how do I verify that my package can be built with bytestring 0.12? There is no GHC releases that bundle that version yet. Is there some flag that could tell it to use a version from Hackage rather than the one included into the GHC distribution?
@minoru If your bounds allow 0.12, and you’ve run cabal update to fetch the latest versions from hackage, then cabal build should pick 0.12 if I’m not mistaken.
And setting the lower bound as @jaror mentioned should force 0.12
@jaror@romes Thank you both! The mystery is already solved, please see earlier comments. Turns out I was specifying a non-existent version to --constrain, but didn't notice it because the error message for "version doesn't exist" looks the same as for "version couldn't be used because it doesn't satisfy constraints". The Universe seem to be pushing me to contribute to Cabal as of late :)
Upgrading the password manager I wrote in #haskell a couple of years ago was surprisingly straight forward. Moved all dependency boundaries into a cabal freeze file. Let's see how that feels moving further.
I've been learning and loving #Haskell. It feels very much like coding in #spreadsheets for some reason. I think it has to do with how the built-in functions are laid out.
I am yet again starting a project in #haskell and having fun getting lost in something fun, but basically causing me to be side-tracked.
I'm working on a simple pixel art editor, but I am excited by #LiquidHaskell to, I think, use refinement types and prove certain properties about my code.