You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like, in SetNumberFormatDigitOptions, if either one returns something other than undefined for the first Get call, we do a second Get to get the real value that we use (from inside GetNumberOption). Is there a reason for this, besides that it was easier to write the spec that way? It would seem more straightforward if we just stuck with the value from the first time we read it out of the object.
The text was updated successfully, but these errors were encountered:
I'm confused; won't GetNumberOption return the fallback if the value resulting from Get is undefined? It seems like this change you made will break the logic.
littledan
added a commit
to littledan/ecma402
that referenced
this issue
Mar 18, 2017
It looks like, in SetNumberFormatDigitOptions, if either one returns something other than undefined for the first Get call, we do a second Get to get the real value that we use (from inside GetNumberOption). Is there a reason for this, besides that it was easier to write the spec that way? It would seem more straightforward if we just stuck with the value from the first time we read it out of the object.
The text was updated successfully, but these errors were encountered: