Ah wait a min! Math.epsilon is dependent on IEEE conformance and hardware and cthulian horrors... Haxe's Float is _always_ 64bits as of today, BUT it's epsilon varies if you use ARM in fast ieee or Intel or whatever PSP thing...
So usually people I met (incl myself) that are doing epsilon based computation either compute the epsilon or use 1e-6 (32b) / 1e-10 (64b) and stick with it...( I favor the second approach so I get inlining )
So I still think tolerating it for abstract would be highly sufficient since Float has a static semantic across platforms, thus allowing various FloatXX flavors to be overloaded.