Skip to content

Commit

Permalink
Clarifies BigDecimal documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
jqno committed Aug 13, 2024
1 parent fbc5104 commit a563c38
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/_errormessages/bigdecimal-equality.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,8 +79,8 @@ If values like `1` and `1.0` *should* be equal then some options are:
}
```
Unfortunately it is difficult to confirm this has been done. This check will then want disabling by suppressing `Warning.BIGDECIMAL_EQUALITY`
and will not catch regressions.
Unfortunately it is imporssible for EqualsVerifier to confirm this has been done. Therefore, you still need to suppress
`Warning.BIGDECIMAL_EQUALITY` in this case.
If performance is important then you will want to consider the costs of using `BigDecimal` and of where and how normalisation
is achieved. Option 2 performs the work when objects are stored in a `HashSet` or used as keys in a `HashMap`. Option 3
Expand Down

0 comments on commit a563c38

Please sign in to comment.