Leonardo Colman Lopes

Closing it as completed since the feature was implemented in #3461. If problems arise again let's open it as a bug :D

They've purposefully ignored this topic for a long time. I gave up on having anything to do with it

I was able to reproduce it here with Kotest 5.8.0. Running all tests in the class still work. This is strictly an IntelliJ-Android-Kotest problem. @nsk90 Were you able to reproduce...

We do have matchers for `compareTo` - `shouldBeEqualComparingTo` Would this solve the issue for different scales? BigDecimal returns 0 for `BigDecimal("1.0").compareTo(BigDecimal("1")` So one could just use `BigDecimal("1.005") shouldBeEqualComparingTo BigDecimal("1.0050000")`

I think so, yes! Now what to call it is tough. Any idea?

`shouldBeSameValue`?

I'm trying to think if mathematically we have a term that means 'this number represents the same value as this one, in totality' And I can only think of `shouldBeNumericallyEquivalentTo`...

So `15.05 shouldBeNumericallyEquivalentTo 15.050000`

Like `shouldBeIgnoringScale` or the one you suggested? Nothing against it at all 😁 go for it

shouldBeEqualIgnoringScale sounds better