forked from extern/nushell
2223fd663a
# Description This makes the help messages cleaner for keyword-style arguments. Before: ``` (optional) else_expression <Keyword([101, 108, 115, 101], Expression)>: expression or block to run if check fails ``` Now: ``` (optional) "else" + <expression>: expression or block to run if check fails ``` # User-Facing Changes Changes how help is printed, so we use slightly different shape names # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. |
||
---|---|---|
.. | ||
benches | ||
src | ||
Cargo.toml | ||
LICENSE | ||
README.md |
nu-plugin
Benchmark
Here is a simple benchmark for different protocol for encoding/decoding nushell table, with different rows and columns. You can simply run cargo bench
to run benchmark.
The relative html report is in target/criterion/report/index.html
.