Closed andreasabel closed 10 months ago
You can specify doctest-version: >=0
in your configuration file.
You can specify
doctest-version: >=0
in your configuration file.
Yes of course. But good tooling has sensible defaults. Defaulting to an outdated version isn't a good default.
Removing the constraint would lead to the following workflow:
doctest: True
does the job.doctest
would go looking for a way to configure the doctest version used by haskell-ci.Currently we have:
haskell-ci
pinning to an outdated version.Currently we have:
The doctests fail.
Do we? If they worked, they should continue to work.
And that "if it worked, and nothing is explicitly changed, it should work" is my philosophy. You may upgrade haskell-ci
(which may have different major version used by default), or change the haskell-ci
config or do something else - then things may break (or unbreak) - but you'll know what you have changed.
You won't make me change my mind on this.
Do we? If they worked, they should continue to work.
If they weren't broken, I wouldn't have gone to the effort of changing Haskell CI. Let me see if I can recover the evidence...
Got it!
doctest
bound: https://github.com/andreasabel/generic-lens/pull/1/commits/e8428f78c9cb7c9b609d785dc3c1b2549bb72214If they weren't broken,
You added GHC-9.8 CI, so you did change something.
doctest
bound has been rotting too quickly. Just use the latest version by default. Can always be overwritting bydoctest-version
option incabal.haskell-ci
.Closes https://github.com/haskell-CI/haskell-ci/issues/690