Re: Instant.now(Clock) and InstantSource

2024-06-04 Thread Naoto Sato
+1 for not deprecating the method that takes Clock. It would give existing users unnecessary warnings. Naoto On 6/4/24 12:17 AM, Stephen Colebourne wrote: On Mon, 3 Jun 2024 at 22:25, Kurt Alfred Kluever wrote: It feels a bit strange that you can't pass an `InstantSource` to `Instant.now(...

Re: Instant.now(Clock) and InstantSource

2024-06-04 Thread Stephen Colebourne
On Mon, 3 Jun 2024 at 22:25, Kurt Alfred Kluever wrote: > It feels a bit strange that you can't pass an `InstantSource` to > `Instant.now(...)`, but you _can_ pass a `Clock` (which of course has a > "useless" `ZoneId` when creating an `Instant`). Therefore, I'd like to > propose one of the foll

Instant.now(Clock) and InstantSource

2024-06-03 Thread Kurt Alfred Kluever
Hi folks, It feels a bit strange that you can't pass an `InstantSource` to `Instant.now(...)`, but you _can_ pass a `Clock` (which of course has a "useless" `ZoneId` when creating an `Instant`). Therefore, I'd like to propose one of the following API changes: 1) adding `Instant.now(InstantSource)