Simon Hengel

I think I used this a long time ago to kind of soft deprecate versions `< 2`. As long as `cabal` gives strong preference to the latest version then I...

Just to doublecheck, the issue was that `doctest` did not properly handle response files, right? Or is there anything else going on? - `--with-repl` is a great improvement that I'm...

Similar to what @dundargoc already mentioned, the patch level can be derived from the Git history with: ```bash git rev-list v9.1.0..HEAD --count --invert-grep \ --grep '^runtime' \ --grep '^CI' \...

For completeness, `patch-level.h` can be generated with [`patch-level.sh`](https://gist.github.com/sol/54d60fecb7e892c57d3232e50d78867c) via ```bash echo "#define PATCH_LEVEL $(./patch-level.sh)" > patch-level.h ``` which as of https://github.com/vim/vim/commit/b975ddfdf96644b8df808415dee36f99abd48753 produces ```c #define PATCH_LEVEL 538 ```

@idontgetoutmuch I don't think the seed was fixed for those examples before this PR.

This is the contact surface of Hspec with QuikCheck: https://github.com/hspec/hspec/blob/main/hspec-core/src/Test/Hspec/Core/QuickCheck/Util.hs https://github.com/hspec/hspec/blob/main/hspec-core/src/Test/Hspec/Core/QuickCheck.hs#L66-L105

@MaximilianAlgehed so the idea is to have a time budget for each individual test case, right? QuickCheck then would use up the whole time budget. As a consequence, if you...

> @Bodigrim there is really nothing stopping us doing both! As I said before, I don't see myself using it. There already is `within`, which I think can be used...

Hey 👋 Did you try to implement this in terms of `System.Timeout.timeout`? Also, look at https://github.com/hspec/hspec/issues/889#issuecomment-2125837311.

@parsonsmatt I think we just need one extension that adds `--timeout=` and I guess some timeout combinator `Timeout.apply :: Seconds -> SpeWith a -> SpeWith a` (or maybe `Timeout.seconds ::...