• Home
  • Raw
  • Download

Lines Matching +full:crate +full:- +full:example

1 regex-syntax
3 This crate provides a robust regular expression parser.
5 [![Build status](https://github.com/rust-lang/regex/workflows/ci/badge.svg)](https://github.com/rus…
6 [![Crates.io](https://img.shields.io/crates/v/regex-syntax.svg)](https://crates.io/crates/regex-syn…
7 [![Rust](https://img.shields.io/badge/rust-1.28.0%2B-blue.svg?maxAge=3600)](https://github.com/rust
12 https://docs.rs/regex-syntax
17 There are two primary types exported by this crate: `Ast` and `Hir`. The former
28 ### Example subsection in regex-syntax
30 This example shows how to parse a pattern string into its HIR:
46 This crate has no `unsafe` code and sets `forbid(unsafe_code)`. While it's
47 possible this crate could use `unsafe` code in the future, the standard
48 for doing so is extremely high. In general, most code in this crate is not
53 The standard for using `unsafe` in this crate is extremely high because this
54 crate is intended to be reasonably safe to use with user supplied regular
57 in the compiler or the standard library. (Since `regex-syntax` has zero
61 ### Crate features
63 By default, this crate bundles a fairly large amount of Unicode data tables
70 [in the "Crate features" section of the documentation](https://docs.rs/regex-syntax/*/#crate-featur…
76 of the large number of features exposed by this crate, a `test` script is
83 The primary purpose of this crate is to provide the parser used by `regex`.
84 Specifically, this crate is treated as an implementation detail of the `regex`,
87 Since this crate is an implementation detail of `regex`, it may experience
89 possible because this crate is _not_ a public dependency of `regex`.
91 Another consequence of this de-coupling is that there is no direct way to
97 Stated differently, the coupling between `regex` and `regex-syntax` exists only