quasicomputational

I'm not aware of a user-agent, no. But it's something I was doing in an extension, and, if it's an idea I've had, I'm sure plenty of other people have...

Well, my use-case was where the data is not precious and discarding it was, at worst, mildly annoying rather than breaking; false positives causing data loss in edge cases (which...

Decoupling dependencies from the core would also make it a bit easier to do smoke testing and porting to new GHCs or particularly massive dependency bumps. `aeson` in particular would...

It's basically that `doctest` needs to be pointed towards the right things - it has no idea where v2-style package databases, includes, etc are. Invoking it with `cabal v2-exec` is...

`auto` is also good when you're taking an enum-like argument, as [dhall-to-cabal does with `--print-type`](https://github.com/dhall-lang/dhall-to-cabal/blob/master/exe/Main.hs). I'd like to replace it with something better, that isn't `Read`-based and comes with out-of-the-box...

I don't have a good understanding of what the Haskell stuff for Github Actions actually does to set the environment up (but I suspect I'm going to have to learn...

Right. If the theory's correct, this is really the collision of two issues: 1. `doctest` is not friendly to cross-compilation. I think that this might be for reasons, but I've...

Yeah, it's not like it's a blocker or anything. But this is a standard header and it is still a bit of ugliness to work around - especially since, on...

I've not managed to use `dhall-to-cabal` in anger yet - two attempts have bounced off so far for various reasons, but it's still on my to-do list and I do...

I had a further look at this and I concluded that we probably need an intermediate type; something like ``` data IfThen a b = IfThen Condition a b data...