Hi,
You are correct that it is initialized lazily (or not at all if
getInstant is overridden
and not delegated to), However constructing a new MutableInstant instance
does not initialize it from a clock, the value in both cases is {epochSecond=0,
nanoOfSecond=0}, similarl to the default implementa
Hi,
The semantics are quite different now, right? Before, the instant ivar was
initialized on object instantiation, 'my instant is when I was created.'
Now, it's value is a random amount of time after instantiation. How can
that be right?
Gary
On Wed, Jun 13, 2018 at 6:14 AM wrote:
> Repositor
