With any new DateTime object in any language I usually look at its persistent fields to judge what the memory and access characteristics are.

In case of Temporal it looks like that Chrome goes the JavaScript Date way as it only holds the timestamp:

extern class JSTemporalInstant extends JSObject { nanoseconds: BigInt; }

And then calendrical fields are computed on the fly. Is this correct?