commit | f0e05d05c89790095fa9c12279f153164d760bb1 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <[email protected]> | Wed Feb 17 04:32:09 2021 +0000 |
committer | Automerger Merge Worker <[email protected]> | Wed Feb 17 04:32:09 2021 +0000 |
tree | 61cbc999afbb44a39051d64970ec4715eba50b3e | |
parent | 4b059e71be45309a137a905cf64913a5bbd2fb9f [diff] | |
parent | c0e3b1379cc5931d3ad0abd3f9b25f32c1ba1c03 [diff] |
Snap for 7149879 from 985c813f8f642419249c0a5b1f6a40b12c5e1074 to sc-release am: c0e3b1379c Original change: https://googleplex-android-review.googlesource.com/c/platform/external/rust/crates/unicode-xid/+/13594000 MUST ONLY BE SUBMITTED BY AUTOMERGER Change-Id: I85d745364c5fb1039dd631467dfcba8bac5a8f39
Determine if a char
is a valid identifier for a parser and/or lexer according to Unicode Standard Annex #31 rules.
extern crate unicode_xid; use unicode_xid::UnicodeXID; fn main() { let ch = 'a'; println!("Is {} a valid start of an identifier? {}", ch, UnicodeXID::is_xid_start(ch)); }
unicode-xid supports a no_std
feature. This eliminates dependence on std, and instead uses equivalent functions from core.