rok commented on pull request #12528:
URL: https://github.com/apache/arrow/pull/12528#issuecomment-1062278061


   > So it should be possible to implement the expected semantics without 
exposing any additional options to the user, possibly by examining the two 
`earliest` and `latest` values and choosing the best one.
   
   Currently we only raise and we want to control raise vs earliest/latest. 
That would mean exposing additional option I think?
   
   Or are you proposing to not raise? I think that's a valid for nonexistent, 
but I'm not sure about ambiguous. E.g. ceil(t) falls to exact moment of DST 
switch and could return t or t + dst_offset. We can take the same approach here 
and see if users eventually complain :). Here's an [ambiguous example from 
date.h](https://howardhinnant.github.io/date/tz.html#ambiguous_local_time).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to