1.5 KiB
1.5 KiB
Backend internal interview (rust) - improved
How to used
cargo run -- can be replaced for generated binaries with
- target/debug/be-technical-interview-rust (for debug build)
- target/release/be-technical-interview-rust (for release build)
For help
cargo run -- -h
For input file input.txt
cargo run -- -i input.txt
In quiet mode
cargo run -- -i input.txt -q
if output path is provided, results will be saved in provided path,
without quiet mode info is printed to terminal
cargo run -- -i input.txt -o /tmp/output.txt
Use config path. Batch processing in parallel (one thread for each target)
cargo run -- -c config.toml
Config file content
be_quiet = false
[[targets]]
input = "input.txt"
[[targets]]
input = "input_2.txt"
If output path is provided, out_overwrite can be used (true or false) to append conten or rewrite.
By default:
- out_overwrite is true
- reg_exp* is set as
pub const DEFAULT_REG_EXP: &str = r"(\d+) (\w+) (\d+)";
reg_exp can be provided but as a regex expresion from string, if it can not be converted parser exit.
To solve this
be_quiet = false
[[targets]]
input = "input.txt"
# \ has to be escaped
reg_exp = "(\\d+) (\\w+) (\\d+)"
[[targets]]
input = "input_2.txt"
Caution
Command line options have precedence over config path settings.
Be careful with the combinations