Frank Yung-Fong Tang 0fe508c5f0 change notation to "standard" ... I do not believe this setup is correct if we use notation: "compact". in https://tc39.es/proposal-intl-numberformat-v3/out/numberformat/diff.html#sec-setnfdigitoptions notation is "compact" mnsd is undefined mxsd is undefined mnfd is undefined mxfd is undefined hasSd is false hasFd is false needSd is false needFd is false so step 23 else block will be run Set intlObj.[[RoundingType]] to morePrecision. then in step 23 of https://tc39.es/proposal-intl-numberformat-v3/out/numberformat/diff.html#sec-initializenumberformat ``` If roundingIncrement is not 1 and numberFormat.[[RoundingType]] is not fractionDigits, throw a RangeError exception. ```		2022-01-07 13:17:50 -05:00
..
annexB	RegExp.prototype.compile from other realm should throw TypeError from other realm.	2021-09-10 15:04:11 -04:00
built-ins	Fix incorrect argument	2022-01-07 13:14:27 -05:00
harness	Remove harness file, arrayContains.js	2021-11-01 12:55:10 -04:00
intl402	change notation to "standard"	2022-01-07 13:17:50 -05:00
language	Add identifier tests for private class fields specifically	2022-01-05 14:24:20 -05:00