As you've perhaps heard, recently the async-await feature landed on the Rust beta branch. This marks a big turning point in the usability story for Async Rust. But there's still a lot of work to do. As we mentioned in the main post, the focus for the Async Foundations WG in the immediate term is going to be polish, polish and (ahem) more polish.
In particular, we want to take aim at a backlog of strange diagnostics, suboptimal performance, and the occasional inexplicable type-check failure. This is a shift: whereas before, we could have laser focus on things that truly blocked stabilization, we've now got a large set of bugs, often without a clear prioritization between them. This requires us to mix up how the Async Foundations WG is operating.
So how do you deal with a large pile of issues, all of which are important but none of which are vital? One at a time, of course.
The way we've chosen to organize this is something we call focus issues. We're trying to keep a small number of issues tagged as focus issues at any given time. As we close them, we'll pick new ones to replace them. The number of these issues depends on mentoring bandwidth and on how many people are hacking -- as a rule of thumb, they should mostly all be assigned and actively progressing at any given time.
We also have a secondary set of issues called on deck issues. These are the candidates to become focus issues as focus issues are completed. If you'd like us to consider fixing something sooner rather than later, you can add the "on deck" label yourself, along with a bit of context explaining why you think this issue is more important than the rest.
You can help in two ways:
#wg-async-foundations on Zulip. Maybe we can find something
for you.此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。