-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
questions (possible bugs) re specification/language identity #3207
Comments
For the first part, we think this can be clarified by replacing the second sentence with
though it may read better to move those around somewhat. |
Our editor call conversation got cut short, but the solution we were working on for the second part is adding "together with the GlobalSymbolRegistry".
|
In 5.2.7 Identity, paragraph 2 says:
But paragraph 5 tells us that Booleans are "without specification identity". So how can specification identity determine the result of a comparison of two Booleans?
Also, paragraph 3 says:
The latter sentence seems wrong to me. First, the phrase "language identity of ECMAScript language values" is odd, given that paragraph 5 tells us that many ECMAScript language values are without language identity.
So perhaps what the sentence in question means is something more like "[these algorithms] determine whether or not specific ECMAScript language values have language identity". But that isn't true either. E.g., if you look at the Note in SameValueNonNumber, it implies that Null/Undefined/BigInt/String/Boolean aren't "compared by identity", but that's far short of determining that they don't have language identity. Worse, that Note indicates that all Symbols can be compared by identity, implying that that they all have identity, which is true of specification identity but not language identity. (But maybe this is a bug in SameValue.)
Probably the sentence's use of "determine" is the problem. Maybe it should be more like "[these algorithms] rely on the concept of language identity [defined in paragraph 5]."
The text was updated successfully, but these errors were encountered: