New Assertion API

[mindplay-dk]

Experimental (BREAKING) API change:

• would allow assertions to log more than one Fact
• potentially (not implemented) allows for async assertions.

[mindplay-dk]

@dimatakoy Well, as you can see, I didn't go ahead with these changes, because I wasn't sure I wanted to add that complexity. I think there would be simpler ways to add support for async assertions, which was the primary motivation for this attempted change.

I want something that's really open-ended, unopinonated, and easy to explain - for the most part that just means using functions with one responsibility, as opposed to objects with multiple different methods.

I'm not sure what you want this "meta" stuff for - you're kind of going straight for the "what" without really explaining "why", so I'm not really following what it is you're trying to achieve.

By better error reporting, you mean assertions could include information from context? Context is just there to provide a means of getting dependencies to your test implementations. Assertions shouldn't be coupled to context, I don't think - it's an optional test implementation detail, just a very small utility that lets you reuse test subject bootstrapping. If that makes sense? 🙂