Uli Bubenheimer

Confirmed fixed in 20.0.0. Good news, but did this really have to take 7 years and 12 major releases?

Right now, for Android 11 DP1.1, handling the user selection in settings asks for code similar to the following, which should be possible to simplify via changed EasyPermissions APIs: ```java...

I have created a related Android platform issuetracker issue regarding the incorrect behavior of `shouldShowRequestPermissionRationale()`: https://issuetracker.google.com/issues/151427074

I'm not sure what the best APIs might be to add to capture the new settings-related workflows in Android 11. I'd assume that related Android 11 APIs are still in...

For reference, here's the URL for other Android 11 permission changes, in addition to background location permission changes: https://developer.android.com/preview/privacy/permissions

Thanks, those are valid points regarding the more hypothetical "relative time" use case, I did mean arbitrary reference point chosen by my own code. On that note, if I did...

Long vs. Int: the motivation for this feature request is memory footprint. Int has half the memory footprint of Duration's Long (on many platforms). My use case is limited to...

Could it make sense to provide some of the general-purpose date/time APIs for usage with epoch-based milliseconds without the extra step of a throwaway CompactInstant conversion? And keep those APIs...

@OrhanTozan thank you for the pointer. @dkhalanskyjb: > Do you mean, just a separate library artifact that only contained a function to convert the number of epoch milliseconds into an...

My needs for Java-agnostic datetime handling may expand over time, that would provide reasonable justification for incorporating the full datetime artificat.