Reading the docs and attempting simple implementations, I'm still not sure how to use these, since I keep getting panics. I'm going to search Github to see people using these successfully to figure out what I am missing.

The documentation currently is not very clear as to how it computes things, and one reason I think is that nearly all the example just compare whether 1.0 is approximately equal to 1.0 which isn't very illustrative.

It would be good if there were examples at the crate level showing the differences between the various macros that illustrate when one should use abs_diff_eq! vs `relative_eq!

UnivEq proves that "equals correctly defines the equality".
But I could neither find a definition of what that should mean, nor documentation on how that is proved. All implementation of equals must be correct according to equals contract. Do you simply talk about implementations that aren't the default reference equality? Or what?

This issue was born while trying to better understand htt

If you pass two equal primitive to the array comparison method it'll return true. Perhaps add this at the top:

if (!Array.isArray(arrA) || !Array.isArray(arrB)) {
  return false
}

Provide additional comparision against mutation testing, by pitest framework.

Let's see who is the boss agian!

Expected Behavior

Documentation should be use focused and have more user focused discussion and answers. For example, like adding a faq w