..Also, why does this work in the first place? I thought Haxe didn't support "either-or" for type parameters. I guess this is sort of a hack that works because any Int is also a valid Float? If you reverse the order of the constraint it stops working: `<T:Int, Float>`