![bors[bot]'s avatar](/assets/no_avatar-849f9c04a3a0d0cea2424ae97b27447dc64a7dbfae83c036c45b403392f0e8ba.png "bors[bot]"){kind=avatar}
Merge #72
72: Bump criterion from 0.3.3 to 0.3.4 r=jbreitbart a=dependabot[bot] Bumps [criterion](https://github.com/bheisler/criterion.rs) from 0.3.3 to 0.3.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/bheisler/criterion.rs/blob/master/CHANGELOG.md">criterion's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>All notable changes to this project will be documented in this file.</p> <p>The format is based on <a href="http://keepachangelog.com/en/1.0.0/">Keep a Changelog</a> and this project adheres to <a href="http://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p> <h2>[Unreleased]</h2> <h3>Added</h3> <ul> <li>Added support for benchmarking async functions</li> <li>Added <code>with_output_color</code> for enabling or disabling CLI output coloring programmatically.</li> </ul> <h3>Fixed</h3> <ul> <li>Criterion.rs will now give a clear error message in case of benchmarks that take zero time.</li> <li>Added some extra code to ensure that every sample has at least one iteration.</li> <li>Added a notice to the <code>--help</code> output regarding "unrecognized option" errors.</li> <li>Increased opacity on violin charts.</li> <li>Fixed violin chart X axis not starting at zero in the plotters backend.</li> <li>Criterion.rs will now automatically detect the right output directory.</li> </ul> <h3>Deprecated</h3> <ul> <li><code>Criterion::can_plot</code> is no longer useful and is deprecated pending deletion in 0.4.0.</li> <li><code>Benchmark</code> and <code>ParameterizedBenchmark</code> were already hidden from documentation, but are now formally deprecated pending deletion in 0.4.0. Callers should use <code>BenchmarkGroup</code> instead.</li> <li><code>Criterion::bench_function_over_inputs</code>, <code>Criterion::bench_functions</code>, and <code>Criterion::bench</code> were already hidden from documentation, but are now formally deprecated pending deletion in 0.4.0. Callers should use <code>BenchmarkGroup</code> instead.</li> <li>Three new optional features have been added; "html_reports", "csv_output" and "cargo_bench_support". These features currently do nothing except disable a warning message at runtime, but in version 0.4.0 they will be used to enable HTML report generation, CSV file generation, and the ability to run in cargo-bench (as opposed to <a href="https://github.com/bheisler/cargo-criterion">cargo-criterion</a>). "cargo_bench_support" is enabled by default, but "html_reports" and "csv_output" are not. If you use Criterion.rs' HTML reports, it is recommended to switch to <a href="https://github.com/bheisler/cargo-criterion">cargo-criterion</a>. If you use CSV output, it is recommended to switch to <a href="https://github.com/bheisler/cargo-criterion">cargo-criterion</a> and use the <code>--message-format=json</code> option for machine-readable output instead. A warning message will be printed at the start of benchmark runs which do not have "html_reports" or "cargo_bench_support" enabled, but because CSV output is not widely used it has no warning.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/bheisler/criterion.rs/commits">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores ) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Co-authored-by:dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Please register or sign in to comment