Add test:Intl.NumberFormat using "currency" style and "compact", "engineering", or "scientific" notations.

[ben-allen]

Related PR: tc39/ecma402#925

fix #4259

[ptomato]

Thanks!

[trflynn89]

Hi @ben-allen - question about this test when the notation is "compact". In that case, wouldn't resolvedOptions.maximumFractionDigits be 0?

In the constructor, we have mnfdDefault=0 and mxfdDefault=3. But when we go into SetNumberFormatDigitOptions, we end up setting needFd to false here:

21. If roundingPriority is "auto", then
    a. Set needSd to hasSd.
    b. If needSd is true, or hasFd is false and notation is "compact", then
       i. Set needFd to false.

hasFd is false (because the test doesn't specify minimumFractionDigits or maximumFractionDigits), and notation is "compact", so needFd becomes false.

needSd is similarly false, so we end up setting both intlObj.[[MinimumFractionDigits]] and intlObj.[[MaximumFractionDigits]] to 0:

24. If needSd is false and needFd is false, then
    a. Set intlObj.[[MinimumFractionDigits]] to 0.
    b. Set intlObj.[[MaximumFractionDigits]] to 0.

[iamstolis]

Hi @ben-allen - question about this test when the notation is "compact". In that case, wouldn't resolvedOptions.maximumFractionDigits be 0?

I agree that maximumFractionDigits should be 0 when notation is "compact". So, I have created the corresponding issue (#4349).