cloud-hypervisor/vendor/registry-40351f815f426200/unicode-xid
Samuel Ortiz d5f5648b37 vendor: Add vendored dependencies
We use cargo vendor to generate a .cargo/config file and the vendor
directory. Vendoring allows us to lock our dependencies and to modify
them easily from the top level Cargo.toml.

We vendor all dependencies, including the crates.io ones, which allows
for network isolated builds.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-06-04 17:51:52 +02:00
..
scripts vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
src vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
.cargo-checksum.json vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
Cargo.toml vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
COPYRIGHT vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
LICENSE-APACHE vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
LICENSE-MIT vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
README.md vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00

unicode-xid

Determine if a char is a valid identifier for a parser and/or lexer according to Unicode Standard Annex #31 rules.

Build Status

Documentation

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));
}

features

unicode-xid supports a no_std feature. This eliminates dependence on std, and instead uses equivalent functions from core.

crates.io

You can use this package in your project by adding the following to your Cargo.toml:

[dependencies]
unicode-xid = "0.0.4"