4 ms·
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"
by giornogiovanna 7y ago
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.
- hexane360 7y agoMy 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"
- 62747478182 7y ago> Literally everyone else uses prefix await, so this will be a problem. Kotlin uses `.await()`.
- empath75 7y agoIf you’re able to figure out how to write working rust code, you can learn how to google where ‘await’ goes.