Lines Matching +full:to +full:- +full:regex
1 regex-syntax
5 [](https://github.com/rus…
6 [](https://crates.io/crates/regex-syn…
7 [](https://github.com/rust…
12 https://docs.rs/regex-syntax
19 expressions back to their concrete syntax while mostly preserving its original
21 expression that is amenable to analysis and compilation into byte codes or
23 structure of the regular expression. While an `Hir` can be converted back to
24 its equivalent concrete syntax, the result is unlikely to resemble the original
30 This example shows how to parse a pattern string into its HIR:
49 performance critical, since it tends to be dwarfed by the time it takes to
54 crate is intended to be reasonably safe to use with user supplied regular
55 expressions. Therefore, while there may be bugs in the regex parser itself,
57 in the compiler or the standard library. (Since `regex-syntax` has zero
65 or all of these data tables. If a regular expression attempts to use Unicode
67 to the `Hir`.
70 [in the "Crate features" section of the documentation](https://docs.rs/regex-syntax/*/#crate-featur…
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`,
85 and is primarily developed for the needs of `regex`.
87 Since this crate is an implementation detail of `regex`, it may experience
88 breaking change releases at a different cadence from `regex`. This is only
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
92 compile a `regex::Regex` from a `regex_syntax::hir::Hir`. Instead, one must
93 first convert the `Hir` to a string (via its `std::fmt::Display`) and then
94 compile that via `Regex::new`. While this does repeat some work, compilation
97 Stated differently, the coupling between `regex` and `regex-syntax` exists only