Rob Elliot
02/03/2025, 8:01 PMdave
02/03/2025, 8:06 PMRob Elliot
02/03/2025, 8:11 PMkotlin.time
not kotlinx.time
, and annotated as @WasExperimental
which suggests it isn't any moredave
02/03/2025, 8:13 PMJasonB
02/03/2025, 9:09 PMkotlin.time
is for benchmarksJasonB
02/03/2025, 9:09 PMJasonB
02/03/2025, 9:10 PMJames Richardson
02/03/2025, 10:38 PMRob Elliot
02/04/2025, 8:30 AMI think they have very different use cases - kotlin.time is for benchmarksAnd detecting timeouts, but yes, I see, and I see the confusion with kotlinx.time which looks much more familiar to a java.time user. Thanks all, helped me learn.
CLOVIS
03/09/2025, 1:12 PMNo, it's for logging events and timeouts. kotlinx-benchmark is for benchmarksis for benchmarkskotlin.time
Todd
03/29/2025, 1:06 AM5.seconds
and then converting to a java duration when necessary. The main reason is I think the api for declaring the duration is a lot cleaner and more readable.