Ask about user's opinion about the speed with which Rust evolves

[Kobzol]

The previous question was just... bad. This variation is hopefully more clear. I also think that it makes sense to ask this as the first question in this segment about Rust features.

Fixes: #248

[llogiq]

I fear that this question might be a bit too broad to be useful. E.g. I'd wish Rust would evolve faster in some directions, but slower in others... (Though given the question as is, I'd likely answer that I'm happy with the current pace).

What are we measuring here and what actionable learning do we expect from this?

[Kobzol]

Good point, but I'm not sure if we can design a question that would enable us to find out the "pace opinion" for multiple areas (which areas?). Probably people will always want performance improvements, bug fixes etc., but might not want new features.

Regarding the motivation of this question, it's a bit complicated. It originally started with a question that follows this one, about features that people would like to see stabilized. This question was a bit controversial last year (see discussion in #243 if you're interested). What we would really like to find out are areas that Rust users struggle with, but it's not easy to figure that out with a closed answer set, and analyzing thousands of very liberally written open answers is also not something that we are good at. So we decided (as a compromise) to just include some basic list of most commonly requested features in the following question (and then we also have a question about problematic areas).

Then, out of this question, came up the idea about figuring out if people want any Rust features to be added at all. So what we are essentially measuring is the vibe about how fast Rust changes, if people want us to add new features or not, and how much has our complexity budget has already been spent. I think that this can be used to judge whether some new language features (which might be good ideas on its own) might perhaps be just too big of a change (like the recent is pattern matching discussion, or also the effect system comes to mind).

I think that the current set of questions about features/problems/pace of development is not great, but so far I have been struggling to figure out a better way to combine them together and derive what we actually want to ask our users.

[Kobzol]

Rebased and modified the perex + the first answer.

[apiraino]

OK, I'm still not completely sold to this question but let's try asking either way, let's see if interesting data comes out :)