Make --join the default

[stephentoub]

When running lots of benchmarks, the first time I run them I invariably forget to include --join on my command line invocation, resulting in the benchmark results being spread across a long history of spewed output. I then take the time to run all the benchmarks again, this time with --join, as doing so is much less time consuming then finding all the results and manually cobbling them together into one table. Personally, I've never once wanted the non-joined behavior, and it'd be great from my perspective if --join were the default.

[Scooletz]

I agree with what @stephentoub stated above. I don't rerun my benchmarks and I do spend my time on

finding all the results and manually cobbling them together into one table

but having --join as a default would be great.

[adamsitnik]

@AndreyAkinshin any thoughts on that?

if we are going to implement it we should remember to allow the users to disable this behavior by passing --join false which is going to require a workaround (tmds/Tmds.LinuxAsync#29)

[YegorStepanov]

Bump, this is the top 6 problem by likes.

We can work around the bug by making .Join is Nullable<bool> (like Adam did in another repository).

"" -> true
"--join" -> true
"--join=true" -> true
"--join=false" -> false

[timcassell]

Join as default would be nice, but I think it should work properly for all cases first. Are you still going to work on #2163 @YegorStepanov?

[YegorStepanov]

It should work properly for all cases first

In what cases does it not work?

Are you still going to work on #2163

Yep, sorry for not answering for a long time!

[timcassell]

In what cases does it not work?

The issues that #2163 claims to fix (multiple types).

[AndreyAkinshin]

I agree with @timcassell: it makes sense to merge #2163 first.