* Note that when the offset of a stored absolute Time becomes large, precision of a double might not be enough for the required * resolution of a Time. A double has around 16 significant digits (52 bit mantissa). This means that when we need to have a * double Time with TimeUnit.BASE as its unit, the largest value where the ms precision is reached is 2^51 = 2.3E15, which is * around 71000 years. This is sufficient to store a date in the 21st Century with a BASE or an Epoch offset precise to a * microsecond. ## ##FLOATTIME## FloatTime *
* Note that when the offset of a stored absolute Time becomes large, precision of a float might not be enough for the required * resolution of a Time. A float has around 7 significant digits (23 bit mantissa). This means that when we need to have a float * time that is precise to microseconds, the Time value should not go above 2^22 = 4.0E6. This is not enough to store * Epoch values that are in the order of magnitude of 2E12 ms! So feeding System.TimeInMillis() to a FloatTime with * TimeUnit.BASE as its unit is not having the required precision. At best, a FloatTime can store TimeUnit.BASE or * TimeUnit.EPOCH values with real calendar values with a precision of several minutes. ##