pub struct MatchOptions {
pub case_sensitive: bool,
pub require_literal_separator: bool,
pub require_literal_leading_dot: bool,
}
Configuration options to modify the behaviour of Pattern::matches_with(..)
Fields
case_sensitive | Whether or not patterns should be matched in a case-sensitive manner.
This currently only considers upper/lower case relationships between
ASCII characters, but in future this might be extended to work with
Unicode.
|
require_literal_separator | If this is true then path-component separator characters (e.g. / on
Posix) must be matched by a literal / , rather than by * or ? or
[...]
|
require_literal_leading_dot | If this is true then paths that contain components that start with a .
will not match unless the . appears literally in the pattern: * , ?
or [...] will not match. This is useful because such files are
conventionally considered hidden on Unix systems and it might be
desirable to skip them when listing files.
|
Methods
Constructs a new MatchOptions
with default field values. This is used
when calling functions that do not take an explicit MatchOptions
parameter.
This function always returns this value:
MatchOptions {
case_sensitive: true,
require_literal_separator: false.
require_literal_leading_dot: false
}
Trait Implementations
Derived Implementations
Keyboard shortcuts
- ?
- Show this help dialog
- S
- Focus the search field
- ⇤
- Move up in search results
- ⇥
- Move down in search results
- ⏎
- Go to active search result
Search tricks
Prefix searches with a type followed by a colon (e.g.
fn:
) to restrict the search to a given type.
Accepted types are: fn
, mod
,
struct
, enum
,
trait
, typedef
(or
tdef
).