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
The const implementation from #507, and the existing enum implementation, does not properly compare objects. Objects are compared in a loosely-typed manner (==), which also results in a loosely-typed comparison of all members.
This behavior is incorrect, and results in spec violations. For example, "string" == true returns true, despite being clearly invalid - both the type and content are completely different.
The text was updated successfully, but these errors were encountered:
The
const
implementation from #507, and the existingenum
implementation, does not properly compare objects. Objects are compared in a loosely-typed manner (==
), which also results in a loosely-typed comparison of all members.This behavior is incorrect, and results in spec violations. For example,
"string" == true
returns true, despite being clearly invalid - both the type and content are completely different.The text was updated successfully, but these errors were encountered: