carbon-language/carbon-lang

mirror of https://github.com/carbon-language/carbon-lang.git synced 2026-10-01 22:02:45 +01:00

Files

T

History

josh11bandChandler Carruth 58c106010c Updates to design docs to reflect accepted proposals (#3254 )

Includes proposals:
- #990
- #2188
- #2138
- #2200
- #2360
- #2760
- #2964
- #3162

Also tries to use more precise language when talking about:
- implementations, to avoid confusing `impl` declaration and definitions
with the `impls` operator used in `where` clauses, an issue brought up
in #2495 and #2483;
- "binding patterns", like `x: i32`, and "bindings" like `x`.

---------

Co-authored-by: Chandler Carruth <chandlerc@gmail.com>

2023-09-23 15:53:07 +00:00

..

comments.md

Added design of comments in design docs (#2641 )

2023-03-30 09:51:47 -07:00

numeric_literals.md

Explicit 'one or more' for digits in non-decimal integers. (#2936 )

2023-06-22 15:55:10 -07:00

README.md

Added info on symbolic tokens in design docs (#2657 )

2023-06-01 22:16:13 -07:00

string_literals.md

Added newline example and clarifications for string_literals.md (#2966 )

2023-07-06 18:33:49 +00:00

symbolic_tokens.md

Updates to design docs to reflect accepted proposals (#3254 )

2023-09-23 15:53:07 +00:00

whitespace.md

Fix cross-file links in non-proposal files (#1010 )

2022-01-07 11:00:21 -08:00

words.md

Treesitter parser (#2902 )

2023-07-13 18:28:28 +00:00

README.md

Lexical conventions

Table of contents

Lexical elements

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:

a maximal sequence of whitespace characters
a word
a literal:
- a numeric literal
- a string literal
a comment
a symbolic token

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