Simon Hengel

My first thought was that this is somehow related to https://gitlab.haskell.org/ghc/ghc/-/issues/20670. However, I can't reproduce this with a regular `cabal repl` GHCi session. So not sure. @andreasabel it doesn't really...

Conceptually this could be a feature. A defaults definition could use this to provide holes that the user can fill with a local file (to work around the fact that...

Unless we can identify how this is harmful I would leave the code as it is and instead focus on user features: - inline defaults - arguments for defaults We...

@fisx Is the assumption something like: 1. The user presses `ctrl-c`, `doctest` receives SIGINT but the forked `ghci` does not receive SIGINT 2. `ghci` is still busy with something so...

Not sure what to do here. My first impression is "too much hassle for no gain". But then again, what may be no gain for me, may be important to...

@jsermeno I don't have a good solution here. If you are actually testing your code (rather than using Doctest to make sure that examples in your documentation do actually work),...

I agree that this would be useful. Not sure when I would have time to work on this, but patches are welcome of course. Reporting (`/src/Runner.hs`) is a little bit...

@munro I'm excited to hear that you like both `doctest` and `hspec`. I'll write a more through reply when I can free up some time. But one quick question, both...

For me this does not have high priority for the following reasons: - The current approach is not tied to any particular testing framework and is robust. We had [`test-framework-doctest`](http://hackage.haskell.org/package/test-framework-doctest)...

I don't know of a better way to do this. But if you have some module `Foo.hs` that imports `System.Posix.Syslog`, the following should work: ``` main = doctest ["-idist/build/", "-isrc",...