Nikolai Vazquez
Nikolai Vazquez
@thomaseizinger I believe https://github.com/rust-lang/cargo/issues/1982 would remove the need to pass an explicit feature flag
This seems to be same issue as https://github.com/nvzqz/divan/issues/61. See https://github.com/rust-lang/rust/issues/133491 for upstream discussion.
I plan for this to land in 0.2 in the following form: ```rs #[divan::bench_group(types = [Vec, HashSet, BTreeSet, LinkedList])] fn group(group: divan::BenchGroup) { group .bench("bench1", || { ... }) .bench("bench2",...
Divan used to set CPU affinity on initial start but that naïve approach ran into the issue of multi-threaded benchmarks not running on separate cores. That issue can probably be...
Would something like this work well for you? ```rs /// Sets default options for all benchmarks and groups in the current module. #[divan::bench_options] fn divan_options(options: &mut divan::BenchOptions) { options.threads([1, 2,...
Yeah they would be inherited like the current `#[divan::bench_group]` behavior.
I didn't consider this initially but you're right that there should be a way to focus benchmarks on throughput rather than latency. Right now the output prioritizes minimum time spent....
I hadn't actually considered a no-op benchmark to be a legitimate scenario, but you make a good point about it making sense to have for initial benchmark code setup/testing. I'd...
I didn't design the `args` option to work with a generic type argument. I'm in the middle of a refactor and may be able to fix this issue as a...
Update on this: I have a solution that will land in 0.2.