Alex J Burke

I've been very bad at commenting, but aside from my original observation I think many others have contributed their use cases and further justifyied the utility. As it stands though...

- late -> large

We did a very basic thing along these lines for the `` "starts with"/"end with" assertions so there is definitely precedent for this now. I'd guess one of the difficultues...

@papandreou think these new example are very clean, but I don't think this need be a release blocker - we can always follow up with this.

I’ve made a start updating the docs for this. Side thought, of we’re going to clarify this case of an assertion that executed a function perhaps we want to do...

@papandreou sigh "commits" 🙃

@dasilvacontin would you have been more likely to avoid this trap if the "to throw" documentation were as in this PR: https://github.com/unexpectedjs/unexpected/pull/493

This assertion has come up in conversations a couple of times recently: I'm going to be bold and say I feel a consensus is growing that we might need to...

@papandreou did we manage to tackle this when we added the string diff collapsing stuff?

Aliases for "to throw" are already supported - see the documentation for the assertion [here](http://unexpected.js.org/assertions/function/to-throw/). The word "satisfying" is not something defined for "to throw", but if we added it...