Mastodawn

fun superoptimizer result from @hyperoptimizer, this occurs in ImageMagick

@regehr @hyperoptimizer Is this intentional or did someone just choose epsilon too small/mistankenly forgot a type cast?

@CanLehmann @hyperoptimizer I don't know how to tell that, but I'll ask Zhengyang for a file:line so we can look (he's not here often)

@regehr @CanLehmann @hyperoptimizer likely it originates from some sort of type-generic code of some sort.

@steve @regehr @hyperoptimizer That would make sense, otherwise I would be surprised why it would be written like this.

@CanLehmann @regehr @hyperoptimizer most likely some "compare with tolerance" macro.

Don't forget the glorious way of doing this thanks to C/C++: using scientific notation!

bool test(short x) { return x == 1e3; }