Rename the benches/ directory to benchmark/ or benchmarks/

[postmodern]

Rational

• benches is ambiguous and may confuse English-as-Second-Language (ESL) programmers.
• benches is only 3 letters shorter than benchmarks, so it's not significantly shorter. benchmark (singular) is only 2 letters longer than benches.

[sunjay]

Or at least give us the option to configure it in Cargo.toml! 😄

[alexcrichton]

@sunjay you should be able to list out benchmarks via [[bench]] in Cargo.toml, no?

[sunjay]

I mean it would be nice if it were possible to specify something like:

# section and field names are just examples, not necessarily what the actual names would be
[bench]
location = "benchmarks"

You're right that you can already do this on a case by case basis, but it would be nice to just be able to modify the search path so all the awesome auto discovery features of cargo still work.

[alexcrichton]

Ah yes that's what I figured, and makes sense to me.

[link2xt]

As any target, [[bench]] can have path setting specified: https://doc.rust-lang.org/cargo/reference/cargo-targets.html#configuring-a-target

[epage]

Considering the command is cargo bench and the table for configuring them is bench, calling the directory that hosts them benches doesn't seem far off.

I'd also be concerned about different packages changing this for little benefit, making it harder to jump from project to project.

As for migrating the ecosystem from one to another, I don't see it paying off enough benefit with the name bench so entrenched to make up for the cost to the ecosystem for doing so.

I'm proposing to the cargo team that we close this.

[epage]

Also, I feel like there was a similar issue for making the tests/ configurable but not finding it atm

[weihanglo]

This could possibly be generalized to “being able to set the path of target auto-discovery”, though I agree it's more beneficial to have a community-wide project layout convention.

Closing this. Let us know if there is something not working well without this feature.

[epage]

Found the related issue: #12672