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
|
@ -499,7 +499,7 @@ pub fn byte_lit(lit: &str) -> (u8, usize) {
|
|||
}
|
||||
}
|
||||
|
||||
pub fn binary_lit(lit: &str) -> Rc<Vec<u8>> {
|
||||
pub fn byte_str_lit(lit: &str) -> Rc<Vec<u8>> {
|
||||
let mut res = Vec::with_capacity(lit.len());
|
||||
|
||||
// FIXME #8372: This could be a for-loop if it didn't borrow the iterator
|
||||
|
@ -517,7 +517,7 @@ pub fn binary_lit(lit: &str) -> Rc<Vec<u8>> {
|
|||
}
|
||||
}
|
||||
|
||||
// binary literals *must* be ASCII, but the escapes don't have to be
|
||||
// byte string literals *must* be ASCII, but the escapes don't have to be
|
||||
let mut chars = lit.bytes().enumerate().peekable();
|
||||
loop {
|
||||
match chars.next() {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue