Skip to content

Conversation

@alexandre-daubois
Copy link
Member

Fix #18930

Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would swap the main purpose and the "big advantage" below. (I would also not use "big advantage", that's too subjective)
The main feature of the class is to be bound to the global clock managed by the component, the strictness (and consist behavior across versions of PHP) is bonus.
We might also tell that all clock implementations in the component return a DatePoint?

@alexandre-daubois
Copy link
Member Author

Thank you for your comment, I reworded the whole section by taking your feedback into account 👍

Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, here are some proposals

@alexandre-daubois alexandre-daubois force-pushed the date-point branch 2 times, most recently from 0c23e95 to 38698e2 Compare September 27, 2023 12:35
Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once my two remaining comments are handled, thanks!

@OskarStark
Copy link
Contributor

Thank you Alexandre.

@OskarStark OskarStark merged commit 79ea13c into symfony:6.4 Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Clock] Add DatePoint: an immutable DateTime implementation with stri…

5 participants