His reasoning is at best subjective, there is nothing sound about considering only one use case.
The only reasoning for it is to imitate chaining of methods, but then what will become of read-ability?
await is not some simple method invocation, it actually changes the flow of program.
I can imagine having few chains of async ops, but I do not believe it would justified something like
x.foo().await.bar().await.qa or even
The language syntax should be consistent, and not favoring someone’s personal taste.
I like making convenient builders that would allow me to configure something via long chain of method invocations, but I wouldn’t do something like that for multiple async operations.
Instead I’d prefer something like
let foo = await x.foo();
let bar = await foo.bar();
You can argue that I can go by with
await <expression> is more natural in Rust as
return and other keyword operators
await should follow these examples, not
P.s. in the end the idea might be raised, but it should be formalized as RFC instead of making it a big surprise to community.
P.s.s I’m pretty sure I’m not alone who thinks of
.await as mistake too