Use consistent terminology for byte string literals
Avoid confusion with binary integer literals and binary operator expressions in libsyntax
This commit is contained in:
parent
69c3b39d0d
commit
405c616eaf
25 changed files with 69 additions and 69 deletions
|
@ -82,8 +82,8 @@ pub enum Lit {
|
|||
Float(ast::Name),
|
||||
Str_(ast::Name),
|
||||
StrRaw(ast::Name, usize), /* raw str delimited by n hash symbols */
|
||||
Binary(ast::Name),
|
||||
BinaryRaw(ast::Name, usize), /* raw binary str delimited by n hash symbols */
|
||||
ByteStr(ast::Name),
|
||||
ByteStrRaw(ast::Name, usize), /* raw byte str delimited by n hash symbols */
|
||||
}
|
||||
|
||||
impl Lit {
|
||||
|
@ -93,8 +93,8 @@ impl Lit {
|
|||
Char(_) => "char",
|
||||
Integer(_) => "integer",
|
||||
Float(_) => "float",
|
||||
Str_(_) | StrRaw(..) => "str",
|
||||
Binary(_) | BinaryRaw(..) => "binary str"
|
||||
Str_(_) | StrRaw(..) => "string",
|
||||
ByteStr(_) | ByteStrRaw(..) => "byte string"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue