Simon Hengel

@andreasabel before moving forward with this, I will dogfeed it for a little bit longer.

As a general note, vendoring `HUnit` has already caused friction for users. Personally, I try to only vendor internal dependencies, that do not leak to the public API of a...

Did you try to verify whether the same thing happens with GHCi? Sent from my iPhone > On 6 May 2015, at 10:33 pm, Nickolay Kudasov [email protected] wrote: > >...

Try to run that QuickCheck property in GHCi, passing the exact same arguments to GHCi as you passed to doctest.

I think this is an extension of #174. As we currently don't share the scope between properties and examples, code like ```haskell -- >>> let x = 1 -- prop>...

There are two things here: 1. Should `hpack` accept. 2. How should `hpack` render it. Regarding (1), should `hpack` accept something like: ```yaml tested-with: GHC: - 8.6.3 - 8.4.4 -...

@nikita-volkov Doctest is agnostic about what kind of statements you feed it. So it can not differentiate import statements from expressions that produce output. This has the advantage that >...

> recording the absolute path instead of the relative path should fix the problem. I think this would require Template Haskell, I'm not aware of a way to achieve this...

@moodmosaic thanks a lot for taking a look at this. > could we align with our [style guidelines](https://github.com/hedgehogqa/haskell-hedgehog/blob/master/STYLE_GUIDE.md) That makes sense, yes 👍 > I can take care of it...

I'm looking into it right now.