181b42bfce
Summary: We don't need to have those constants because this functionality is available in STL via `std::numeric_limits<YourParticularFloatType>::infinity()` (or `::min()` and `::max()`). At the same time usage of `kFloatMax` was replaced with `Infinity` (which is a different value). Using `max` instead of `Infinity` was an attempt to mimic iOS/UIKit model where `Infinity` and `NaN` values usually are not being used. However, now this does not seem like a good idea. This concept is not used anywhere else (even in CK which is totally incompatible with it) and de-facto in RN we use it only in few places. So, let's use Infinity in places where it's logically appropriate. Reviewed By: mdvacca Differential Revision: D15155191 fbshipit-source-id: 4d24350c7540cec074a8b040d7c13f257aa812e7 |
||
|---|---|---|
| .. | ||
| platform | ||
| tests | ||
| BUCK | ||
| ColorComponents.h | ||
| Geometry.h | ||
| React-graphics.podspec | ||
| Transform.cpp | ||
| Transform.h | ||
| conversions.h | ||