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
Explicitly mention that unpaired surrogates are illegal. This is particularly relevant for Java, C# and javascript programmers, where they are legal in strings.
Document supported escape sequences in the documentation for string literals, not just in the grammar specification. Or at least link it from there.
Document which encoding is used to store strings (UTF-8? UTF-32?). The documentation points out a 1GB (or is it 1GiB?) limit, but without knowing the encoding that's difficult to interpret.
Explicitly mention that unpaired surrogates are illegal. This is particularly relevant for Java, C# and javascript programmers, where they are legal in strings.
Document supported escape sequences in the documentation for string literals, not just in the grammar specification. Or at least link it from there.
Document which encoding is used to store strings (UTF-8? UTF-32?). The documentation points out a 1GB (or is it 1GiB?) limit, but without knowing the encoding that's difficult to interpret.
An example at https://www.edgedb.com/docs/edgeql/literals#strings is wrong:
There should be no
r
in the response lineThe text was updated successfully, but these errors were encountered: