Survey of "High Impact" Features

[tkaitchuck]

I have attempted to raise a couple of things that might fall into that category in the past. On the lang side:

Pub(test) visibility modifier

I often find myself wanting a visibility modifier which makes the function pub for when compiled under test but not otherwise. Motivation I realize this wades into the white box vs black box testing debate and tests that test internal components should be unit tests and not integration tests. But sometimes it still feels like it would help. The situation where I most often encounter this is when I am testing a component which is a "middle" layer. (i.e.: It receives a public api call, does some …

On the libs side:

Is cfg-if going to be pulled into std?

cfg-if seems strictly superior to cfg!. Because instead of generating dead code, it doesn't get included in the first place. (Hence it can be used for platform/os specific things). While cfg-if is already one of the top 10 crates and is maintained by the libs team, it really seems like the sort of thing that should be in std.

Additionally: stabilizing cargo bench:

Stabilize `#[bench]` and `Bencher`?

And Rustfmt

Tracking issue for RFC 2437, "Rustfmt stability"