Adam Sitnik

Hi @MichalPetryka You can provide MSBuild arguments for each job. Sth like: ```cs using BenchmarkDotNet.Configs; using BenchmarkDotNet.Environments; using BenchmarkDotNet.Jobs; using BenchmarkDotNet.Running; namespace BenchmarkDotNet.Samples { public class Program { public static...

I agree that it would be nice to expose `UseMonoRuntime` as built-in BDN feature. We could add `mono7.0` moniker and support it with `--runtimes` so `--runtimes net7.0 mono7.0` would compare...

Hi @MichalPetryka Is there any chance you could share a repro?

It should be now fixed with #2071

> I am willing to implement this but wanted to get some confirmation that this is a desirable feature for the project. If given the go-ahead, I can follow up...

> Ability to specify sets of benchmarks in filters `--filter` accepts multiple strings. Example: ```cmd --filter Bench1.A Perf2.B ``` > Friendly names for --coreruns in reports This should be easy...

I am going to transfer this issue to BDN repo as all the feature requests are BDN feature requests.

@scalablecory is is true for both `ValueTask` and `ValueTask` or just `ValueTask`? @stephentoub do you have any suggestions for a solution with minimum overhead?

@timcassell When running sync benchmarks the engine should not be doing any async work (as it could affect the results by introducing some noise). We should most probably have two...

hello @bazzilic ! I am sorry but we have made no progress.