The intention of the core.time.Instant class is to provide a mutable equivalent of java.time.Instant (which is immutable). This allows for us to create high precision (sub-millisecond) timestamps while reusing some objects and remaining garbage free.
So in short, no, our implementation provides functionality that the JDK class doesn’t have so we cannot replace it (at least not without loss of functionality). > On Jun 3, 2020, at 18:59, Volkan Yazıcı <[email protected]> wrote: > > Can we also replace core.time.Instant with java.time.Instant? > >> On Sun, May 24, 2020 at 11:57 PM Volkan Yazıcı <[email protected]> >> wrote: >> >> May I second that with {Bi,Tri}Consumer classes as well? >> >>> On Sun, May 24, 2020 at 11:21 PM Gary Gregory <[email protected]> >>> wrote: >>> >>> Hi All, >>> >>> Can we drop org.apache.logging.log4j.util.Supplier from master for 3.x and >>> replace its usage with java.util.function.Supplier? >>> >>> Gary
