Should InitializeNumberFormat throw a TypeError when "roundingIncrement" isn't supported?

[anba]

InitializeDateTimeFormat and ToDateTimeOptions throw a TypeError when dateStyle/timeStyle is mixed with the other date-time component options. Is that error similar to the situation when "roundingIncrement" is used with non-fractional rounding and should therefore InitializeNumberFormat be changed to throw a TypeError instead of a RangeError? The relevant step is:

23. If roundingIncrement is not 1 and numberFormat.[[RoundingType]] is not fractionDigits, throw a RangeError exception.

---

I don't have any preference here, I've just spotted this when implementing the error behaviour for "roundingIncrement".

[romulocintra]

Adding it for next TG2 plenary meeting agenda

[sffc]

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-03-17.md#should-initializenumberformat-throw-a-typeerror-when-roundingincrement-isnt-supported-68

Conclusion:

• Change line 23 (the line in Andre's post) to TypeError.
• @ryzokuken to consider adding this to the ECMA-402 style guide.