-
Notifications
You must be signed in to change notification settings - Fork 27
Update duration to unsigned fields + specification updates #507
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
Conversation
Running this on v8 introduces more failures. What does Boa say?
|
It seems like there are two issues: one is that |
Oh shoot, we should adjust tests so that this fails then. EDIT:
I have to double check that. I haven't gotten around to testing directly in Boa yet. (But I'd assume the same thing as above) |
I'm fine with the general concept for adding some f64 support in partials and the edges, but why would that be needed rather than emulating the shifting maximum/minimum in IsValidDuration? Per the specification, we should only really be receiving integers. A |
Integer-valued floats, which aren't the same thing since for large integers they will get clipped. We should have tests for built-ins/Temporal/Duration/prototype/total/precision-exact-mathematical-values-6 and built-ins/Temporal/Duration/prototype/total/precision-exact-mathematical-values-7, which currently fail with failures like this:
I haven't fully investigated why. I think it's due to this problem but it might be something else! |
Let me know when you'd like me to test it against v8 again I would like to avoid new failures; though if those tests can't be replicated in |
The above fix should address the range issue. I'm not entirely sure about the others breaks yet though that aren't related to the range issue, so it may be worth rerunning it. |
No new test failures! |
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.
Looks good!
} | ||
} | ||
|
||
impl TimeDuration { |
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.
note: deleting this does not affect v8
This PR makes a large portion of updates from #366 without bringing in the
bnum
crate.The changes are primarily as follows:
There are a handful of API changes linked to this change that are primarily related to moving addition variations that were using the old TimeDuration.