Yam Marcovic

@NikhilVerma Thank you for that potential fix. I hoped it would allow me to move on with my project, after already having invested in the transition to this library, but...

I've examined the code and saw the tricks employed in the decorators. The quickest fix to this issue IMO would be to add the following lines to `mutationaction.ts`, in the...

Since the repo has not been updated in over a year, I have forked it and applied the update mention above, so that state and getters can be accessed from...

The main point is to get the output of `exception.ToString()`, as it already contains the entire exception tree. From what I saw, at the point where the error details reach...

@bradwilson Oh nice. I see that `xunit.v3.runner.utility` already depends on `xunit.abstractions`. So if I understand correctly, I could simply utilize `IFailureInformation` to print out the full hierarchy that's already been...

Note that mock behavior should be different if it's mocking Unix or Windows filesystems. On Windows, you can't delete a file that's in use; you should get an `IOException` in...

+1 Also for `TEMPLATE_LIST_SCENARIO` and such (i.e. template analogues for BDD).

@elfenpiff I think that it is indeed risky to be able to construct an invalid `function_ref`, especially in so easy a manner. For your `callMe()` example, I'd probably replace that...

@mossmaurice 1. Check. 2. Good argument IMO. One could accept a `function_ref` only when one is sure this won't be stored, otherwise (by default, maybe) accept a `function`. 3. Good...

My feeling here is that it isn't possible to provide function_ref in a way that is both elegantly usable, as well as foolproof. Same as _view classes. But I'm okay...