Simon Hengel

> Not really, I mean, it seems to still be a valid choice to have per test rendering timeout, even if I can understand how useful it would be to...

> I've wanted this ability as well, so 👍🏿 @srid it will take a while until I'll be able to get back to this, but quickly, what do you need:...

@srid that sounds like (1), right? This PR is (2). However, I think (1) will be easier. There are some complications with this PR that I'll try to note down...

I think this describes a specific implementation rather than a user story. From what I understand, you want to store/retrieve configuration values in the spec monad. Is that correct? If...

I think in the simplest case we can just store a function in our monad stack that essentially maps type representations to Maybe values of some existential. On set/modify we...

Actually we want it scooped to specific parts of the spec tree. So I guess we'll want to go with a reader and ask/local instead. But something along those lines.

@parsonsmatt Hspec makes a distinction between “constructing a spec tree” and “executing a spec tree”. So the question is “when exactly do you want to access additional configuration?”. - At...

#713 proposes a solution.

`hspec-expectations` builds on top of `HUnit` and it does not depend on `hspec-core` or any other parts of `hspec`. This is by design so that `hspec-expectations` can be used with...

@kozross if you want to understand how Hspec hooks work, here are a couple of things that might not be obvious at first: 1. Every spec item gets a *subject*,...