Josh Burkart

So I guess the question is: should I make a real PR with updated default matchers, etc.?

@ujh seems to be MIA? @povilasb What's the path forward?

Great crate! I agree the messages could be improved a bit... I'm not sure that nice sentences can always be produced, though, without a large amount of effort... What if...

Also, in addition to perhaps tweaking how the matchers display themselves, one thought I had was to add a third (possibly optional) "Explanation" or "Details" section, in addition to "Expected"...

The Swift Hamcrest implementation prints error messages like this: ``` assertThat(CGPoint(x: 5, y: 10), hasProperty("x", closeTo(5.0, 0.00001))) // ✓ assertThat(CGPoint(x: 5, y: 10), hasProperty("y", closeTo(0.0, 0.00001))) // GOT: (5.0,10.0) (property...

Thanks for the info! I'll update this issue if I figure something out...

Would love to get this in, was just looking for this feature! Anything we're waiting on? @brendanzab?

This would be really great to have! Approximately comparing nested `struct`s/`enum`s is a pretty common use case when writing tests for numerical computing applications. @tylerreisinger Do you think the implementation...

Bummer! Sadly this was written in a much older version of Mathematica (7?) and hasn't been updated... If you can figure out an improvement please send a PR!

Ah, actually, I remember noticing the speed difference too. Yep I'm not sure how to work around this either, other than by using smaller notebooks... Sorry!