-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editorial: Replace AddDateTime with AddDate #2882
Conversation
@anba If you're not in too much of a hurry with this, I'd like to wait until after the TC39 meeting next week when it's clear if there is agreement on removing user-defined calendars. |
No, there's no hurry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically looks fine, there's a discrepancy in internal slot names though. Thanks!
Adding a zero-time duration in AddDateTime means that the output date-time record has the same time components as the input date-time record. This allows to directly read the time components from the input date-time record.
Calling AddDateTime with a zero-time duration is equivalent to directly calling AddDate.
Rebased to apply on main. |
Implements the editorial improvements from the previous commits, in order to make the reference code follow the spec text more closely.
Added a commit to reflect the spec text changes in the polyfill as well, though it has no discernible effect. |
Replacing AddDateTime with AddDate makes it easier (for implementers) to see why it's okay to skip all time duration normalization steps.
e283b59:
9e220c7:
0739c71:
aee3538:
5776d1a: