一些关于Rust在2019年的思考

每年，我们都会要求社区撰写有关他们希望在Rust的明年路线图中看到的内容的博客文章。 A call for Rust 2019 Roadmap blog posts 这是我在2019年的Rust帖子。

Rust 2021: 成熟

今年也有点特别; 在2018年，我们对Rust推出了大约三年的版本时间表。 所以现在不仅是思考2019年的好时机，而且也是2020年和2021年的时候。 Rust在2015年的一些思考是关于“稳定性”的。 Rust在2018年的一些思考是关于“生产力”的。我希望Rust在2021年的一些思考能够是关于“成熟”的。

为了实现这一目标，这是我们在2019年所需要的。

No new features(新特性，但不是新事物)

Emphasis on “new” here. What do I mean by this? Well, there are a few features that are in the pipeline that I do think should land:

这里强调“新”。 这是什么意思？ 好吧，我认为应该落地一些关于 pipeline 的功能：

async/await
GATs
const generics

And possibly(可能的特性)

Specialization

这些功能都不是新的; 我们已经有了他们的基本设计。 这些特征也具有重要意义和基础性; 我们需要 sync/await（或者GATs）来建立一个伟大的网络编程体系，我们需要const、泛型来获得一个优秀的数值系统。

但那之后呢？ 如果可以的话，我更愿意我们受限在2020年或某一年，在这之前暂停主要功能，

我们已经到了一个甜蜜期。 我们总是说Rust 1.0是稳定的而不是完整的。 我想我们正在快速接近完整。

也就是说，我不认为语言团队应该解散; 我认为他们的工作应该过渡到详细说明我们已有的东西。 我不确定我们是否可以在2019年完成 reference 的编写（稍后会详细介绍），但我希望它能够更进一步。 这只能在语言团队的帮助下进行，他们只有在有时间的情况下才能进行这项工作。

Refine the RFC process

The RFC process needs to be significantly re-vamped. Niko wrote a great post on this back in June, and I think it’s really, really, really important. I’d like to work on an RFC to propose this, so if you’re interested, we should talk.

Niko already makes the case and lays out some foundations, so I won’t say more there.

Pay down organizational debt

Consider this section an endorsement of everything boats said. I cannot say it better, so I will just leave it at that.

Figure out documentation sustainability

This year was a bad year for the docs team. The book got shipped, and that was great. We had some people pitch in on the reference, and their work was amazing. Some of the other documentation writers moved on to work on rustdoc, which was important.

But a lot of the goals we wanted to do about writing more docs themselves never came to fruition. For example, contributing to major ecosystem crates? Never happened. The cookbook isn’t done. Rust by Example still languishes. The standard library could use a lot of love.

We just don’t have the people to make this happen. We’ve tried, but nothing has worked. It’s possible that this is simply unfixable, after all, most programmers don’t like writing docs. But I also don’t want to give up on it either. I’m not sure what to do here, but I do know that it is a major problem.

Conclusion

There’s a lot of work to do, and I’m very excited to do it. I think Rust is in an excellent place, and with some work, we can make Rust even more amazing in a year’s time.