# Await Syntax Discussion Summary

**URL:** <https://internals.rust-lang.org/t/await-syntax-discussion-summary/9914>\
**Category:** language design\
**Created:** [April 29, 2019, 9:55pm UTC](https://internals.rust-lang.org/t/await-syntax-discussion-summary/9914 "2019-04-29T21:55:54Z")\
**Posts on this page:** 1\
**Showing post:** 87

<div class="post-metadata">

**Author:** ![epage](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/epage/32/3171_2.png) [@epage](https://internals.rust-lang.org/u/epage)\
**Post date:** [April 30, 2019, 1:17pm UTC](https://internals.rust-lang.org/t/await-syntax-discussion-summary/9914/87 "2019-04-30T13:17:16Z")

</div>

> [@Centril](#):
>
> Note that `.await!()` cannot be implemented as a macro in the literal sense (details, see [https://github.com/rust-lang/rust/issues/51751](https://github.com/rust-lang/rust/issues/51751) and [https://github.com/rust-lang/rust/issues/51719](https://github.com/rust-lang/rust/issues/51719)) . It would need to be special cased in the parser and to keep `await` as a keyword it cannot even interact with name resolution.

From my quick glance, the reasons it can't be a macro are for better error messages and to prevent abuse? I feel I'm missing something because that seems somewhat weak of an argument.

I'm really liking the idea I saw on reddit for UFCS for macros. Instead of creating a special way to declare postfix macros, allow any macro to be postfix.

```rust
let bar = "Hello {}".format!("world");
let bar = foo().async!()?;
let bar = foo().yield!()?;
let bar = foo().r#try!();
let bar = foo().dbg!()?; // EDIT Someone else posted this other good example

```

I assume it isn't an edition-level breaking change to take a keyword and unreserve it if we decide macros can work and postfix macros solve the problems.

---

_[View the full topic](https://internals.rust-lang.org/t/await-syntax-discussion-summary/9914)._
