[threeten-develop] Date Resolvers

[Richard W. <ric...@gm...>]

As I discussed last week with Stephen and James, I emailed the LJC
mailing list to solicit some community feedback about the concept of
Date Resolvers.   Here’s a summary:

* I had 8 replies in total, some on list and some private.
*  All but one felt this was an important feature to have in the API,
with one pointing out that the recent Azure datetime bug was related
specifically to the area of invalid dates.
* One user wasn’t too sure of the usefulness of the 'Push Forward' and
'Push Backward' options.  I’m not sure I can see the scenarios where
they came from - it would be good to know of their origin.
* Some preference for previous valid as the default.
* One user wanted entirely custom date resolvers in order to be able
to process special date rules, but I’m not sure he wouldn’t be better
off with a custom chronology.  Most other people seemed happy with an
enum.
* One person suggested that we throw a checked exception for any
instance when an invalid date is generated.  I think this would be a
terrible idea for a variety of reasons, but I’m reporting it anyhow.

regards,

  Richard