Struct regex_automata::sparse::ByteClass
source · [−]Expand description
A sparse DFA that shrinks its alphabet.
Alphabet shrinking is achieved by using a set of equivalence classes instead of using all possible byte values. Any two bytes belong to the same equivalence class if and only if they can be used interchangeably anywhere in the DFA while never discriminating between a match and a non-match.
Unlike dense DFAs, sparse DFAs do not tend to benefit nearly as much from using byte classes. In some cases, using byte classes can even marginally increase the size of a sparse DFA’s transition table. The reason for this is that a sparse DFA already compacts each state’s transitions separate from whether byte classes are used.
Generally, it isn’t necessary to use this type directly, since a
SparseDFA
can be used for searching directly. One possible reason why
one might want to use this type directly is if you are implementing your
own search routines by walking a DFA’s transitions directly. In that case,
you’ll want to use this type (or any of the other DFA variant types)
directly, since they implement next_state
more efficiently.
Trait Implementations
Return the identifier of this DFA’s start state.
Returns true if and only if the given identifier corresponds to a match state. Read more
Returns true if and only if the given identifier corresponds to a dead state. When a DFA enters a dead state, it is impossible to leave and thus can never lead to a match. Read more
Returns true if and only if the given identifier corresponds to either
a dead state or a match state, such that one of is_match_state(id)
or is_dead_state(id)
must return true. Read more
Returns true if and only if this DFA is anchored. Read more
Given the current state that this DFA is in and the next input byte, this method returns the identifier of the next state. The identifier returned is always valid, but it may correspond to a dead state. Read more
Like next_state
, but its implementation may look up the next state
without memory safety checks such as bounds checks. As such, callers
must ensure that the given identifier corresponds to a valid DFA
state. Implementors must, in turn, ensure that this routine is safe
for all valid state identifiers and for all possible u8
values. Read more
Returns true if and only if the given bytes match this DFA. Read more
Returns the first position at which a match is found. Read more
Returns the end offset of the longest match. If no match exists,
then None
is returned. Read more
Returns the start offset of the longest match in reverse, by searching
from the end of the input towards the start of the input. If no match
exists, then None
is returned. In other words, this has the same
match semantics as find
, but in reverse. Read more
Returns the same as is_match
, but starts the search at the given
offset. Read more
Returns the same as shortest_match
, but starts the search at the
given offset. Read more
Returns the same as find
, but starts the search at the given
offset. Read more
Auto Trait Implementations
impl<T, S> RefUnwindSafe for ByteClass<T, S> where
S: RefUnwindSafe,
T: RefUnwindSafe,
impl<T, S> UnwindSafe for ByteClass<T, S> where
S: UnwindSafe,
T: UnwindSafe,
Blanket Implementations
Mutably borrows from an owned value. Read more