Spec: document string literals #108
Conversation
Copied from google/starlark-go#265 I omitted the implementation notes.
|
Note that it doesn't exactly match the Java implementation, e.g. we reject \a. |
| def" # "abcdef" | ||
| ``` | ||
|
|
||
| An *octal escape* encodes a single byte using its octal value. |
There was a problem hiding this comment.
(The reference to byte here isn't really appropriate for the Java implementation.)
There was a problem hiding this comment.
The rest of the spec mentions that a "string represents an immutable sequence of bytes."
I think it's correct that an octal escape encodes a byte.
Do you have another phrasing to suggest?
There was a problem hiding this comment.
This seems fine for now. Correctly documenting how the Java implementation differs is a complex and subtle project.
spec.md
Outdated
| '\119' # "\t9" = "\11" + "9" | ||
| ``` | ||
|
|
||
| A *hex escape* encodes a single byte using its hexadecimal value. |
There was a problem hiding this comment.
(and hex escapes aren't implemented in Java)
Yes, useless though it may be, every language supports \a thus so should we. |
Copied from google/starlark-go#265
I omitted the implementation notes.