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
Integer-Indexed Exotic Objects internal methods) ([[Get]], [[Set]], [[Delete]], [[Has]], etc.) require special treatment for any string-valued property recognized as a canonical numeric string by CanonicalNumericIndexString that includes silent failure when the property name is out of bounds or non-integer. Non-integer canonical numeric strings include "Infinity", "-Infinity", "NaN", "0.5", "1.2000000000000001", etc.
The text was updated successfully, but these errors were encountered:
gibson042
changed the title
Missing tests for interacting with TypedArray "NaN" properties
Missing tests for interacting with TypedArray non-integer canonical numeric properties
Mar 24, 2022
There should also be coverage for edge cases like "1.2000000000000001" vs. "1.2000000000000002", which are numerically equal but only one of which is a canonical numeric string in any given implementation (although which has canonical status is implementation-defined because Number::toString step 5 does not uniquely define the least significant digit of s) and therefore the other can be used as the name of properties not subject to special treatment. For example, the following expression is required to be true:
Discovered by an XS bug: Moddable-OpenSource/moddable#886
Integer-Indexed Exotic Objects internal methods) ([[Get]], [[Set]], [[Delete]], [[Has]], etc.) require special treatment for any string-valued property recognized as a canonical numeric string by CanonicalNumericIndexString that includes silent failure when the property name is out of bounds or non-integer. Non-integer canonical numeric strings include "Infinity", "-Infinity", "NaN", "0.5", "1.2000000000000001", etc.
The text was updated successfully, but these errors were encountered: