Home
last modified time | relevance | path

Searched refs:BenchmarkGroup (Results 1 – 4 of 4) sorted by relevance

/external/rust/crates/criterion/src/
Dbenchmark_group.rs78 pub struct BenchmarkGroup<'a, M: Measurement> { struct
86 impl<'a, M: Measurement> BenchmarkGroup<'a, M> { argument
238 pub(crate) fn new(criterion: &mut Criterion<M>, group_name: String) -> BenchmarkGroup<'_, M> { in new()
239 BenchmarkGroup { in new()
368 impl<'a, M: Measurement> Drop for BenchmarkGroup<'a, M> { implementation
Dlib.rs109 pub use crate::benchmark_group::{BenchmarkGroup, BenchmarkId};
1097 pub fn benchmark_group<S: Into<String>>(&mut self, group_name: S) -> BenchmarkGroup<'_, M> { in benchmark_group()
1108 BenchmarkGroup::new(self, group_name) in benchmark_group()
/external/rust/crates/criterion/src/html/
Dmod.rs184 struct BenchmarkGroup<'a> { struct
192 impl<'a> BenchmarkGroup<'a> { argument
193 fn new(output_directory: &Path, ids: &[&'a BenchmarkId]) -> BenchmarkGroup<'a> { in new()
257 BenchmarkGroup { in new()
268 groups: Vec<BenchmarkGroup<'a>>,
551 .map(|(_, group)| BenchmarkGroup::new(output_directory, &group)) in final_summary()
552 .collect::<Vec<BenchmarkGroup<'_>>>(); in final_summary()
/external/rust/crates/criterion/
DCHANGELOG.md25 formally deprecated pending deletion in 0.4.0. Callers should use `BenchmarkGroup` instead.
28 Callers should use `BenchmarkGroup` instead.
113 - Added the `BenchmarkGroup` type, which supersedes `ParameterizedBenchmark`, `Benchmark`,
115 `BenchmarkGroup` performs the same function as all of the above, but is cleaner to use and more