Skip to content
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

Improve string documentation #14

Open
CodesInChaos opened this issue Feb 11, 2024 · 0 comments
Open

Improve string documentation #14

CodesInChaos opened this issue Feb 11, 2024 · 0 comments

Comments

@CodesInChaos
Copy link

  1. Explicitly mention that unpaired surrogates are illegal. This is particularly relevant for Java, C# and javascript programmers, where they are legal in strings.

  2. Document supported escape sequences in the documentation for string literals, not just in the grammar specification. Or at least link it from there.

  3. 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.

  4. An example at https://www.edgedb.com/docs/edgeql/literals#strings is wrong:

    db> select r'hello\nthere'; # raw string
    {r'hello\\nthere'}
    

    There should be no r in the response line

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant