Avoid using shared calendar

Question

Avoid using shared calendar

Opened this issue 9 years ago · 5 comments

Answer 1 · 2017-05-11T04:12:00.000Z

Yeah, this is interesting -- I almost think you need to do a separate library to make this (and timezones) work, because everything will have to use java.time classes like LocalDate instead of the older java.util classes. Important, though, because of lack of thread safety.

Answer 2 · 2017-05-11T04:14:17.000Z

@MrTact Thx for your interest. Yeah actually I've been thinking the same thing. Are you interested in working on it?

Answer 3 · 2017-05-11T04:22:38.000Z

I am! I actually thought about doing something like this, and then realized that someone surely must have done it already.

Then I pulled khronos, thinking "I'll just see if I can add a couple of timezone-related extensions (e.g. "2017-05-10".utc), and then realized that was going to take a lot more work than I anticipated.

Answer 4 · 2017-05-11T07:27:35.000Z

then realized that someone surely must have done it already.

Oh do you mean it's already fixed?

Answer 5 · 2017-05-13T07:00:52.000Z

No, I meant I was thinking about creating a library that used some of Kotlin's cooler features to create a DSL-like wrapper around Java date & time modules. Then I thought someone must have done this already, and someone did -- you :-)

As far as I have been able to find, no one has done a comparable library wrapping LocalDateTime.