Waldemar Kornewald

You mean that laws can change the meaning of the past for a ZonedDateTime (in UTC)?

That’s the point I was trying to provoke. ZonedDateTime in UTC can handle the Instant use-case. Personally, I’d only still want to have the distinction of both types so I...

> First, some personal communication. @wkornewald, you've been very active with this project, and our conversations yielded some very insightful notions. Thank you a lot for this! > > I...

BTW, this really is just a technical improvement suggestion to build more APIs around sealed (it often results in better APIs). It’s by far not my most important issue though....

> * As defined, `ZonedDateTime` is just a collection of functions that are very easy to implement and doesn't offer much over just storing `LocalDateTime` and `TimeZone` separately. If something...

> > 1. It's also not ambiguous with `RegionDateTime` when adding the optional offset > > In which case it would just be a OffsetDateTime right? And all the calendar...

Sorry, noticed too late, moving discussion here. > > Do you have an example? My impression is that it adapts the Instant to ensure that the LocalDateTime+TimeZone is stable. >...

> > Wow. This looks more like a bug. > > This behavior is documented fairly well, and, I think, it's the only consistent way to implement this given the...

Just FYI, in the JavaScript ecosystem the proposed Temporal API also could provide some interesting insights: https://tc39.es/proposal-temporal/docs/ambiguity.html

I've created an initial PR #175 with a sketch of what the API could look like. @dkhalanskyjb @cromefire Would be nice to have your feedback and possibly counter-PRs or PRs...