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

Files

T

Richard SmithandChandler Carruth e257051612 No predeclared identifiers, Core is a keyword (#4864 )

Introduce a principle that the Carbon language should not encroach on
the
developer's namespace. Satisfy this principle by making `Core` a
keyword.

---------

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

2025-02-01 03:03:30 +00:00

comments.md

Added design of comments in design docs (#2641 )

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

numeric_literals.md

Tuples and tuple indexing (#3646 )

2024-01-31 23:42:11 +00:00

README.md

Tuples and tuple indexing (#3646 )

2024-01-31 23:42:11 +00: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

No predeclared identifiers, Core is a keyword (#4864 )

2025-02-01 03:03:30 +00:00

README.md

Lexical conventions

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, with the following exception:

When a numeric literal immediately follows a . or -> token, with no intervening whitespace, a real literal is never formed. Instead, the token will end no later than the next . character. For example, tuple.1.2 is five tokens, tuple . 1 . 2, not three tokens, tuple . 1.2. However, tuple . 1.2 is lexed as three tokens.

README.md

Lexical conventions

Table of contents

Lexical elements