equal() on float #14
Description
Comparing floats is in general critical. Currently equal() expects floating points to be exact. But should it?
Currently with replacing the whole test-suite with my own test-suite that depends on my equal() implementation
it shows that for example creating an Array->range_with_step it fails by comparing two arrays with floating-points.
Should i change equal() in such a way that it allows for some inacurracy in comparing floats by default?
But this change would be global to every comparing of data. But it would be convenient because otherwise comparing
floats is a pain in the ass.