Normative: Limit valid values for DurationFormats to match upcoming limits in Temporal

[ben-allen]

See #157

Upcoming revisions to Temporal will limit the valid values for Temporal.Duration. This commit applies the same limits on valid values for Intl.DurationFormat DurationRecords. Specifically: the absolute values of the values stored in each of the [[Years]], [[Months]], and [[Weeks]] fields cannot exceed 2^32, and the absolute value of the value obtained through converting the values in each of the sub-week fields to seconds and then summing them must not exceed 2^53.

[ptomato]

I'm not involved enough with this proposal to approve the change, but the limits are aligned with the normative change that was approved in Temporal.

[sffc]

TG2 approval: https://github.com/tc39/ecma402/blob/master/meetings/notes-2023-11-16.md#decide-if-upcoming-temporalduration-limits-should-have-an-impact-on-durationformat-157

[ryzokuken]

2023-11-28: This PR achieved TC39-TG1 consensus.

[anba]

Test coverage → tc39/test262#3988

[ben-allen]

Updated to match limits currently set in Temporal. See: tc39/proposal-temporal#2727

@ptomato has pointed me toward tc39/proposal-temporal#2727 (comment) for thoughts on implementation. He's also written a polyfill that implements the limits via string manipulation to run test262 tests against.

@ryzokuken @FrankYFTang

[ptomato]

Note the text in Temporal PR 2727 was not the latest, Anba made some changes to it afterwards.

[ben-allen]

Note the text in Temporal PR 2727 was not the latest, Anba made some changes to it afterwards.

Just pushed a corrected version. Thanks for catching that!

[syg]

Does this change mean BigInt math is not required (just like in Temporal)?

[FrankYFTang]

Could we do the following change to better match Temporal?

1. in ToDurationRecord change

24. If IsValidDurationRecord(result) is false, throw a RangeError exception.

to

24. If IsValidDuration( result.[[Years]] ,  result.[[Months]] ,  result.[[Weeks]] ,  result.[[Days]] ,  result.[[Hours]] ,  result.[[Minutes]] ,  result.[[Seconds]] ,  result.[[Milliseconds]] ,  result.[[Microseconds]] ,  result.[[Nanoseconds]] ) is false, throw a RangeError exception.

and change this part to be the exact text of

7.5.15 IsValidDuration ( years, months, weeks, days, hours, minutes, seconds, milliseconds, microseconds, nanoseconds )
from Temporal spec (probabaly except replacing the "to construct a Temporal.Duration" part to "to construct a DurationRecord"

[FrankYFTang]

Notice, with the PR , some test cases in
https://github.com/tc39/test262/blob/main/test/intl402/DurationFormat/prototype/format/precision-exact-mathematical-values.js

will be invalid and require changes to test the boundary condition and throwing/not throwing in the correct values