News for hackers. Stuff that matters.
Re:A final proposal for Rust await syntax by giornogiovanna on Monday May 06, 2019 @12:30PM (#19840979)
Literally everyone else uses prefix await, so this will be a problem. But,

- this is a lot easier to chain, which is very useful, and

- the "future expansion" might bring a prefix await anyway (although introducing two syntaxes for the same thing might be even worse).

I'd prefer "f await" to "f.await" because it feels a lot less magical and lets me stick to my intuition that "." is just for stuff implemented by the library, but maybe that's just me.

Re:A final proposal for Rust await syntax by hexane360 on Monday May 06, 2019 @01:00PM (#19841349)
My personal preference is for a happy medium between "f await" and "f.await", which is some other character that indicates "special postfix". Sort of like how func() is clearly different from macro!(), we can have "expr->keyword" or "expr.keyword!" to differentiate from "expr.property"
Re:A final proposal for Rust await syntax by 62747478182 on Monday May 06, 2019 @07:14PM (#19844887)
> Literally everyone else uses prefix await, so this will be a problem.

Kotlin uses `.await()`.

Re:A final proposal for Rust await syntax by empath75 on Monday May 06, 2019 @08:34PM (#19845340)
If you’re able to figure out how to write working rust code, you can learn how to google where ‘await’ goes.