add dualizer, no-recursion, yaya-*

[sellout]

Checklist:

• Meaningful commit message, eg add my-cool-package (please don't mention build-constraints.yml)
• At least 30 minutes have passed since uploading to Hackage
• If applicable, required system libraries are added to 02-apt-get-install.sh or 03-custom-install.sh
• (recommended) Package have been verified to work with the latest nightly snapshot, e.g by running the verify-package script
• (optional) Package is compatible with the latest version of all dependencies (Run cabal update && cabal outdated)

The script runs virtually the following commands in a clean directory:

  stack unpack $package-$version # `-$version` is optional
  cd $package-$version
  rm -f stack.yaml && stack init --resolver nightly --ignore-subdirs
  stack build --resolver nightly --haddock --test --bench --no-run-benchmarks

[alaendle]

Cabal-3.12.0.0 (changelog) is out of bounds for:

• no-recursion-0.1.2.2 (^>=3.0.0 || ^>=3.2.0 || ^>=3.4.0 || ^>=3.6.0 || ^>=3.8.0 || ^>=3.10.0). Greg Pfeil [email protected] @sellout. Used by: library

QuickCheck-2.15.0.1 (changelog) (Grandfathered dependencies) is out of bounds for:

• yaya-quickcheck-0.2.0.2 (^>=2.10 || ^>=2.13.2 || ^>=2.14.2). Greg Pfeil [email protected] @sellout. Used by: library

doctest-0.24.0 (changelog) (Simon Hengel [email protected] @sol) is out of bounds for:

• no-recursion-0.1.2.2 (^>=0.16.0 || ^>=0.18.1 || ^>=0.20.0 || ^>=0.21.1 || ^>=0.22.2). Greg Pfeil [email protected] @sellout. Used by: test-suite
• yaya-0.6.2.2 (^>=0.16.0 || ^>=0.18.1 || ^>=0.20.1 || ^>=0.21.1 || ^>=0.22.2). Greg Pfeil [email protected] @sellout. Used by: test-suite
• yaya-containers-0.1.2.1 (^>=0.16.0 || ^>=0.18.1 || ^>=0.20.1 || ^>=0.21.1 || ^>=0.22.2). Greg Pfeil [email protected] @sellout. Used by: test-suite
• yaya-hedgehog-0.3.0.4 (^>=0.16.0 || ^>=0.18.1 || ^>=0.20.1 || ^>=0.21.1 || ^>=0.22.2). Greg Pfeil [email protected] @sellout. Used by: test-suite
• yaya-quickcheck-0.2.0.2 (^>=0.16.0 || ^>=0.18.1 || ^>=0.20.1 || ^>=0.21.1 || ^>=0.22.2). Greg Pfeil [email protected] @sellout. Used by: test-suite
• yaya-unsafe-0.4.1.3 (^>=0.16.0 || ^>=0.18.1 || ^>=0.20.1 || ^>=0.21.1 || ^>=0.22.2). Greg Pfeil [email protected] @sellout. Used by: test-suite

[sol]

@sellout https://github.com/sol/doctest?tab=readme-ov-file#running-doctest-for-a-cabal-package

or better yet, https://github.com/sol/doctest?tab=readme-ov-file#cabal-integration

[sellout]

@alaendle Thanks – I’m already running builds with updated bounds. Should be published on Hackage soon.

@sol I’m not sure what you’re suggesting. I have doctests running via cabal test, which works with the old versions of GHC I support, and makes it easier for contributors to not forget to run them. Is there something wrong with that, or was it just not apparent that my doctests are being tested?

[sol]

@sellout Oh, I see what you’re doing now—very clever! It definitely works, but my point is that you could achieve the same result with just a single shell command, replacing 65 lines of code and configuration.

As for compatibility, the documented approach should work with the GHC versions you’re testing in CI. And when it comes to making sure contributors don’t forget to run doctests—well, that’s exactly what CI is for!

There’s nothing wrong with your setup, but it’s not the documented approach, and maintaining upper bounds for doctest doesn’t seem like the best use of anyone’s time. Just using the latest version makes things simpler and lets you focus on more interesting problems.

[sellout]

@sol Thanks – I see what you mean. Thankfully my cabal files are generated, and I really haven’t had to think about doctests (other than writing them). But every line committed to the repo is a liability. I think my original motivation for that approach was for cabal2nix to create derivations that run the doctests, but I think it’s easy enough to get those to run cabal repl in addition to cabal test, so I’ll look into that (and that code also wouldn’t need to be duplicated for each package, or even repo).