Update on await syntax in Rust

It closes the discussion because it makes it difficult for people who disagree to acknowledge that this problem is real while also arguing that we should hold a different balance of the cost, which makes it still the preferable choice. This decision has been justified well and reflects the “consensus weighting” of the different costs among the members of the language team. There are a few further clarifications regarding some conversations that have arisen in the discussion the last few weeks:

I’m working actively on drafting a stabilization report to propose stabilizing a minimum viable version of async/await in the 1.37 release of Rust.

Source: boats.gitlab.io