A byte escape escape starts with U+0078 ( x) and isįollowed by exactly two hex digits.An escape starts with a U+005C ( \) and continues with one of the Some additional escapes are available in either byte or non-raw byte string
The type of a byte string literal of length n is &'static. The literal, it must be escaped by a preceding U+005C ( \) character.Īlternatively, a byte string literal can be a raw byte string literal, definedīelow. If the character U+0022 is present within Preceded by the characters U+0062 ( b) and U+0022 (double-quote), andįollowed by the character U+0022. It is equivalent to a u8 unsigned 8-bit integerī" ( ASCII_FOR_STRING | BYTE_ESCAPE | STRING_CONTINUE ) * " SUFFIX ?Īny ASCII (i.e 0x00 to 0x7F), except ", \ and IsolatedCRĪ non-raw byte string literal is a sequence of ASCII characters and escapes, U+0027 is present within the literal, it must be escaped by a preceding U+0027 (single-quote), and followed by the character U+0027. Range) or a single escape preceded by the characters U+0062 ( b) and 0x00 to 0x7F), except ', \, \n, \r or \tĪ byte literal is a single ASCII character (in the U+0000 to U+007F Macro_rules! blackhole Byte and byte string literals Byte literalsī' ( ASCII_FOR_CHAR | BYTE_ESCAPE ) ' SUFFIX ?Īny ASCII (i.e. In particular, the literal fragment specifier for by-example macros matches literal tokens with arbitrary suffixes.
Ansi escape sequences rust how to#
The macro itself will decide how to interpret such a token and whether to produce an error or not.
SUFFIX_NO_E : SUFFIX not beginning with e or EĪny kind of literal (string, integer, etc) with any suffix is valid as a token.Ī literal token with any suffix can be passed to a macro without producing an error. * All number literals allow _ as a visual separator: 1_234.0E+18f64 SuffixesĪ suffix is a sequence of characters following the primary part of a literal (without intervening whitespace), of the same form as a non-raw identifier or keyword.
Macro Follow-Set Ambiguity Formal Specification
0 kommentar(er)
