#[non_exhaustive]pub struct ParseOptions {
pub var_order: bool,
pub clause_tree: bool,
pub check_acyclic: bool,
}
Expand description
Options for the parsers
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.var_order: bool
Whether to parse a variable orders
The DIMACS satisfiability formats, for instance, do not natively support specifying a variable order, however it is not uncommon to use the comment lines for this purpose. But while some files may contain a variable order in the comment lines, others may use them for arbitrary comments. Hence, it may be desired to turn on parsing orders for some files and turn it off for other files.
clause_tree: bool
Whether to parse a clause tree (for DIMACS CNF)
If the CNF contains, e.g., five clauses, and one of the comment lines
contains co [[0, 1], [2, 3, 4]]
, then the parsed circuit will have
three AND gates (one with clauses 0 and 1 as input, one with clauses
2, 3, and 4, as well as one with those two conjuncts).
check_acyclic: bool
Whether to check that the circuit is acyclic
The time complexity of this check is linear in the circuit’s size, and therefore rather inexpensive. Therefore, it is enabled by default.
Trait Implementations§
Source§impl Clone for ParseOptions
impl Clone for ParseOptions
Source§fn clone(&self) -> ParseOptions
fn clone(&self) -> ParseOptions
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more