Marc Knaup
08/03/2020, 9:53 PMMiguel Hernández
08/05/2020, 11:17 AMMarc Knaup
08/05/2020, 12:24 PMMiguel Hernández
08/05/2020, 12:44 PMMarc Knaup
08/05/2020, 1:06 PMjava.time
API (which is good) but make it more Kotlin-like.
So far it’s focused on JVM and Darwin (iOS & macOS). Each implementation starts as a wrapper of the platform-specific date/time types and over time more and more functionality can be rewritten into common
so that it’s consistent across platforms and can support more platforms.
The API is probably a bit verbose. It may make sense to get rid of the Nanosecond(s)/Milliscond(s)/Second(s)/etc. classes and to simplify. It should also integrate with Kotlin’s own Duration
class and offer PreciseDuration
as an alternative where floating-point values are not acceptable.
Let me know what you think about it 🙂Miguel Hernández
08/05/2020, 2:18 PMMarc Knaup
08/05/2020, 2:25 PMkotlinx-datetime
it makes sense to stop working on fluid-time
and help migrating to the new library as it matures 😅