Lines Matching refs:char
10 //! `char` values are valid in programming language identifiers.
36 //! single `char` has the XID\_Start or XID\_Continue Unicode property,
66 //! static XID_Continue_table: [(char, char); 763] = [
79 //! consumes 8 bytes, because it consists of a pair of 32-bit `char` values.
97 //! Rust's `char` type is a 21-bit integer padded to 32 bits, which means every
101 //! possible to fit in 5 bytes or even 4 bytes by storing a low char and an
102 //! extent, instead of low char and high char. I don't expect that performance
148 //! caller is required to tokenize their UTF-8 encoded input data into `char`,
149 //! hand the `char` into `ucd-trie`, only for `ucd-trie` to undo that work by
164 //! not specialize for the fact that only 21 of the 32 bits in a `char` are
253 pub fn is_xid_start(ch: char) -> bool {
262 pub fn is_xid_continue(ch: char) -> bool {