I wonder if it would be cool to add special handling to isEquals failures that have the same string output.

It does add the type name in, but even that sometimes doesn’t help. I hit an issue the other day where I had 2 sets that toString’ed the same, and they were both sets, but the elements inside the set were different types

I was thinking of adding a line that explains that toString can have the same output and equals still be false.

yeah, I wonder. I could certainly dive deeper in the case of a map or collection

i found this very inspiring: https://elm-lang.org/news/compiler-errors-for-humans

That would be awesome. I have a bug fix I want to work on but not sure how much time I’ll be able to carve out this week