| commit | 11f33051c20ec4919e54c94e118a186c3cb28db0 | [log] [tgz] |
|---|---|---|
| author | Chih-Hung Hsieh <[email protected]> | Sat Jun 13 22:30:49 2020 -0700 |
| committer | Chih-Hung Hsieh <[email protected]> | Sat Jun 13 22:30:49 2020 -0700 |
| tree | 246dca29209832d5e1735f9a24524afa3f63f752 | |
| parent | 87dc6ff92adda70f6b9f51953fc704a897743990 [diff] |
Do not use relative_install_path * Although working with local atest runs, when running with TH test-mapping test script, the relative_install_path caused test-not-found issues. Bug: 158694974 Test: atest -c --include-subdirs external/rust/crates/unicode-xid Test: manually inspect TH test-mapping output in sandbox.stdout Change-Id: I4dd23de1154657dc6eea3ed72e9ba8b720a1e005
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.
You can use this package in your project by adding the following to your Cargo.toml:
[dependencies] unicode-xid = "0.1.0"