ilya-g
ilya-g
@0legg We have no such plans for 1.3, though nothing seems to prevent providing such support in a separate library.
While the benefit of having `getOrElse` extension over `orElseGet` member with the same signature is clear from the KEEP, it can still cause user confusion when these two functions are...
I'm going to merge this PR text and open new issue for the discussion of this KEEP: #321
Related issue https://youtrack.jetbrains.com/issue/KT-28982
I've noticed some error classes in the output, but probably it's because I'm building docs not on a Mac. Also there are parameter types that are not rendered as links...
It is expected that the string representation of a `FixedOffsetTimeZone` doesn't produce a value that can be found in a time zone database: usually, it's something like `+-hh:mm` and the...
>> Though, it should always be possible to obtain a TimeZone value from such a string, either with kotlinx.datetime, or with java.time. > Can you clarify this bit? The issue...
No, since a `FixedOffsetTimeZone` is a `TimeZone`, a serializer that can serialize a `TimeZone` also accepts instances of `FixedOffsetTimeZone` (but I believe you can try to write one). What could...
`java.time` has the class `ZoneOffset` which is an inheritor of `ZoneId` and combines the functionality of expressing an offset from UTC and using it as a time zone. We decided...
- `FixedOffsetTimeZone` can be used as a time zone, while `UtcOffset` can't. - `UtcOffset` is designated to express an offset from UTC (for example when querying `TimeZone.offsetAt(Instant)` offset value), while...