kleidukos

Logs are a critical thing in production systems and I would like to start a discussion about bringing low-level support for efficient logging into GHC

Hello everyone, Two years ago I created get-tested, a tool that reads your cabal file, extracts the tested-with stanza and produces a test matrix for GitHub Actions. It has served me well to this day, but it also recently received a very useful contribution from @turion, who wrote a reusable Github Action for it! I am extremely grateful for this effort.

Hi everyone, The Cabal development community is sending a call for participation in our quality assurance (QA) programme. We are looking to improve the quality of the software we ship on the Windows platform.

Hi everyone, servant-0.20.1 has a release candidate available! It is a compatibility release to support aeson-2.2.

Hi all, I’ve been working for some time on the Eclair compiler (written in Haskell) and I am now at the point where I need to test the LLVM IR my compiler is generating. How would you approach testing this generated code?

This post demonstrates how to outlaw specific return types from servant APIs. Perhaps we have types that are intended for backend use only, or maybe the types are legal in one API but illegal in another yet the backend code is a monolith. Whatever the reason, we can encode a type-level assertion over a servant API that produces a compile-time error if we ever accidentally add a sensitive type to the API.

A lot of the Rust Haskell interop examples out there are for small, synchronous libraries. They also tend to omit how to actually package the Rust library. We'll take a look at challenges and solutions for how to integrate a Tokio-based Rust library with Haskell.

Generate contextually sensible fuzz tests for servant apps

It’s well known in the Haskell world that type class instances cannot be overridden. When you have an instance in scope, you are stuck with it. Is this a feature? Is this a bug? Maybe either depending on the problem you are facing. I have my own opinions, but let me lay out the case for wanting to be able to override instances.

Hi everyone, The Cabal team would like to ask our users if anyone would object to the Nix Integration being removed (following a reasonable deprecation cycle). It has been reported to us that the feature is non-functional, misleading and the documentation lacking.