My guess: Because people only turn on the features they are actively using. For ergonomics features, that tends to be just people who are testing the feature because nobody “needs” them per se; that is, they’re great to have, but I can get my program working without it.
For example, I didn’t use match default bindings before it was on stable, but I did use global_allocator
and panic_implementation
.
Perhaps the solution is to allow some features to be turned on by default (on nightly only) for some time before we intend to stabilize but after we think the feature is debugged enough. Of course, the tradeoff is that would make nightly programs more likely to be buggy/more likely to experience breakage, but after all, it is nightly…