Bump criterion from 0.3.2 to 0.3.4

[dependabot-preview]

⚠️ Dependabot Preview has been deactivated ⚠️

This pull request was created by Dependabot Preview, and you've upgraded to Dependabot. This means it won't respond to dependabot commands nor will it be automatically closed if a new version is found.

If you close this pull request, Dependabot will re-create it the next time it checks for updates and everything will work as expected.

---

Bumps criterion from 0.3.2 to 0.3.4.

Changelog

Sourced from criterion's changelog.

[0.3.4] - 2021-01-24

Added

• Added support for benchmarking async functions
• Added with_output_color for enabling or disabling CLI output coloring programmatically.

Fixed

• Criterion.rs will now give a clear error message in case of benchmarks that take zero time.
• Added some extra code to ensure that every sample has at least one iteration.
• Added a notice to the --help output regarding "unrecognized option" errors.
• Increased opacity on violin charts.
• Fixed violin chart X axis not starting at zero in the plotters backend.
• Criterion.rs will now automatically detect the right output directory.

Deprecated

• Criterion::can_plot is no longer useful and is deprecated pending deletion in 0.4.0.
• Benchmark and ParameterizedBenchmark were already hidden from documentation, but are now formally deprecated pending deletion in 0.4.0. Callers should use BenchmarkGroup instead.
• Criterion::bench_function_over_inputs, Criterion::bench_functions, and Criterion::bench were already hidden from documentation, but are now formally deprecated pending deletion in 0.4.0. Callers should use BenchmarkGroup instead.
• 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 cargo-criterion). "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 cargo-criterion. If you use CSV output, it is recommended to switch to cargo-criterion and use the --message-format=json 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.

[0.3.3] - 2020-06-29

Added

• Added CRITERION_HOME environment variable to set the directory for Criterion to store its results and charts in.
• Added support for cargo-criterion. The long-term goal here is to remove code from Criterion-rs itself to improve compile times, as well as to add features to cargo-criterion that are difficult to implement in Criterion-rs.
• Add sampling mode option for benchmarks. This allows the user to change how Criterion.rs chooses the iteration counts in each sample. By default, nothing will change for most benchmarks, but very slow benchmarks will now run fewer iterations to fit in the desired number of samples. This affects the statistics and plots generated.

Changed

• The serialization format for some of the files has changed. This may cause your first benchmark run after updating to produce errors, but they're harmless and will go away after running the benchmarks once.

... (truncated)

Commits

• 1bf6f4b Update version number.
• 83b7625 Update dependencies.
• 47b8bac Merge branch 'master' of github.com:bheisler/criterion.rs
• 293cd60 Merge pull request #439 from 38/master
• 7a1385a Only determine the target directory once per execution.
• ea4b958 Merge pull request #456 from rossmacarthur/fix/workspace-target-dir
• 73802de Merge branch 'mkantor-fix-some-typos'
• a581219 Merge branch 'fix-some-typos' of https://github.com/mkantor/criterion.rs into...
• ac0db22 Add warning messages for features that will become optional in 0.4.0. #426
• cac59f2 Formally deprecate things that were previously soft-deprecated.
• Additional commits viewable in compare view

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 commands and options

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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)