mirror of https://github.com/rust-lang/reference
tokens.md: say that lifetime-like tokens can't be immediately followed by '
Forms like 'ab'c are rejected, so we need some way to explain why they don't tokenise as two consecutive LIFETIME_OR_LABEL tokens. Address this by adding "not immediately followed by `'`" to each of the lexer rules for the lifetime-like tokens. This also means there can be no ambiguity between CHAR_LITERAL and these tokens (at present we don't say how such ambiguities are resolved).
This commit is contained in:
parent
1afcfd9c66
commit
7bd81a6a03
|
@ -630,11 +630,14 @@ Examples of reserved forms:
|
|||
|
||||
> **<sup>Lexer</sup>**\
|
||||
> LIFETIME_TOKEN :\
|
||||
> `'` [IDENTIFIER_OR_KEYWORD][identifier]\
|
||||
> `'` [IDENTIFIER_OR_KEYWORD][identifier]
|
||||
> _(not immediately followed by `'`)_\
|
||||
> | `'_`
|
||||
> _(not immediately followed by `'`)_
|
||||
>
|
||||
> LIFETIME_OR_LABEL :\
|
||||
> `'` [NON_KEYWORD_IDENTIFIER][identifier]
|
||||
> _(not immediately followed by `'`)_
|
||||
|
||||
Lifetime parameters and [loop labels] use LIFETIME_OR_LABEL tokens. Any
|
||||
LIFETIME_TOKEN will be accepted by the lexer, and for example, can be used in
|
||||
|
|
Loading…
Reference in New Issue