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
{{ message }}
This repository has been archived by the owner on Sep 27, 2019. It is now read-only.
First, integer literals are -- bizarrely -- not legal on the left side of a field initializer. Named constants that have integer values are legal, which falls under "qualified name". "integer-literal" should be removed.
Second, double-quoted string literals are legal on the left side, provided that they do not contain any evaluated expressions. So "X" would be legal, but "$x" would not. We should add a note to that effect.
The text was updated successfully, but these errors were encountered:
We should note also that there are other restrictions on the contents of the literal strings. For example '123' and '2hello' are not legal; the strings may not begin with a number. I'm not sure exactly what all the restrictions are; we should enumerate them and put them in the spec.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The grammar and semantics of field initializers are not quite right in chapter 10.
First, integer literals are -- bizarrely -- not legal on the left side of a field initializer. Named constants that have integer values are legal, which falls under "qualified name". "integer-literal" should be removed.
Second, double-quoted string literals are legal on the left side, provided that they do not contain any evaluated expressions. So "X" would be legal, but "$x" would not. We should add a note to that effect.
The text was updated successfully, but these errors were encountered: