Nikolai Vazquez

I'm currently prioritizing #10/#42 but I plan to support async benchmarks soon after. In the meantime, it seems folks have gotten acceptable results from just invoking `block_on` within the benchmark....

@thomcc ping

Here's my suggestion for running Divan outside of the benchmark harness: ```rs fn main() { divan::Divan::from_args().run_benches(); } ```

I'm convinced that currently the best way to implement this today would be to ~~ab~~use `async`/`await` to get coroutines so that we can swap out the user's stack between benchmarks....

When supplying arguments to a benchmark, you should think of them more like cases rather than like the kinds of arguments provided by property-based testing frameworks. See [the `args` docs](https://docs.rs/divan/latest/divan/attr.bench.html#args)...

Yeah Divan always formats args according to their `ToString` implementation. I'm open to suggestions for how to make this better. I'm not sure if an `args_name_formatter` option is the right...

Hi! I plan to prioritize async benchmarks after I ship JSON output. 🙂 Follow https://github.com/nvzqz/divan/issues/39 for updates > From reading the docs seems like there are some threading-related configs you...

It would be great if Rust Analyzer could run individual Divan benchmarks, so let me know what's needed on my end in Divan to support this. I think to support...

> I assume most customer bencher are run the same way? My understanding is that Divan is the only one using a `#[bench]` attribute. The other popular benchmarking harnesses are...

This is quite unfortunate, but thanks @jdidion for finding a decent workaround! I'll leave this issue open until this works as expected.