Again, I disagree that this is an issue of "floating point comparison", and I am quite knowledgeable in this domain. You are entitled to your opinion as I am to mine.
Here is an example of something that you cannot do (afaict) in Nim: * [http://stackoverflow.com/a/9850710/263998](http://stackoverflow.com/a/9850710/263998) > Thanks for writing an answer that does not suggest an epsilon. This blog post > I wrote some time ago has more examples of behaviors that may be surprising. > blog.frama-c.com/index.php?post/2011/11/08/Floating-point-quiz – Pascal Cuoq This is a real problem -- not terrible, but surprising and worth knowing. Type-conversion from float64 to float32 is not actually altering the floating-point representation. `==(float32, float32)` is misleading. I do _not_ suggest any correction, but I am recording this for posterity.
