josh11b 58c106010c Updates to design docs to reflect accepted proposals (#3254) %!s(int64=2) %!d(string=hai) anos
..
README.md 6d399c80b0 Added info on symbolic tokens in design docs (#2657) %!s(int64=2) %!d(string=hai) anos
comments.md 33f26bd37b Added design of comments in design docs (#2641) %!s(int64=3) %!d(string=hai) anos
numeric_literals.md 2e7ce09c34 Explicit 'one or more' for digits in non-decimal integers. (#2936) %!s(int64=2) %!d(string=hai) anos
string_literals.md c974a77314 Added newline example and clarifications for string_literals.md (#2966) %!s(int64=2) %!d(string=hai) anos
symbolic_tokens.md 58c106010c Updates to design docs to reflect accepted proposals (#3254) %!s(int64=2) %!d(string=hai) anos
whitespace.md b7df523dc8 Fix cross-file links in non-proposal files (#1010) %!s(int64=4) %!d(string=hai) anos
words.md 1cab6920f2 Treesitter parser (#2902) %!s(int64=2) %!d(string=hai) anos

README.md

Lexical conventions

Table of contents

Lexical elements

The first stage of processing a source file is the division of the source file into lexical elements.

A lexical element is one of the following:

The sequence of lexical elements is formed by repeatedly removing the longest initial sequence of characters that forms a valid lexical element.