commit | 1d0b5ddf71b2a34e7bf94b02bb25de5fc7d6959c | [log] [tgz] |
---|---|---|
author | David LeGare <legare@google.com> | Mon Mar 14 18:36:37 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Mar 14 18:36:37 2022 +0000 |
tree | 2f638b0af631bc4d9825f4ea5d5afa19e188b68a | |
parent | bbfb22ac47e9b342dcf3ba0c7c6b53712a54e619 [diff] | |
parent | bd8e405fbb6cfa58acb6dfcaaa72ca7e1f44b594 [diff] |
Update TEST_MAPPING am: ff2788a6f8 am: 1f27efef5c am: 558b05aab9 am: d9b77fd7cf am: bd8e405fbb Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/unicode-xid/+/2005196 Change-Id: Iaae84c7ccbc8dd9509cd165e9971530835d92288
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.