I find myself somewhat frequently doing: ```val min = LocalTime(hour = 0, minute = 0, second = 0, n...

# kotlinx-datetime

[kevin.cianfarini]

I find myself somewhat frequently doing:

val min = LocalTime(hour = 0, minute = 0, second = 0, nanosecond = 0)
val max = LocalTime(hour = 23, minute = 59, second = 59, nanosecond = 999_999_999)

Would there be any interest in accepting a PR that specifies LocalTime.MIN and LocalTime.MAX like both Instant and LocalDateTime have?

[Dmitry Khalanskiy [JB]]

like both Instant and LocalDateTime have

What do you mean? Neither exposes their MIN and MAX.

Would there be any interest in [...] LocalTime.MIN and LocalTime.MAX

No, because both are error-prone. See https://github.com/Kotlin/kotlinx-datetime/issues/490

[kevin.cianfarini]

> like both Instant and LocalDateTime have

What do you mean? Neither exposes their MIN and MAX.

Yeah, whoops, I meant distant future and past.

No, because both are error-prone. See

Gotcha! I’ll comment in that issue.