ECMAScript No-Stage Proposal. Living Document. J. S. Choi, 2018-12.

This document is not yet intended to be officially proposed to TC39 yet; it merely shows a possible extension of the Core Proposal in the event that the Core Proposal is accepted.

An additional feature – bare awaited calls – would make async function calls terser. It adds another mode to bare style: if a bare-style pipeline step is preceded by a await, then instead of a mere function call, it is an awaited function call. value |> await object.asyncFunction is equivalent to await object.asyncFunction(value). This would be backwards compatible with the Core Proposal as well as all other additional features.

Additional Feature BA is formally specified in in the draft specification.

value
|> # + '!'
|> new User.Message(#)
|> await stream.write
|> console.log;

console.log(
  await stream.write(
    new User.Message(
      value + '!'
    )
  )
);

If a pipeline step starts with await, followed by a mere identifier, optionally with a chain of properties, and with no parentheses or brackets, then that identifier is interpreted to be a bare awaited function call.

That is: if a pipeline is of the form
topic |> await identifier
or topic |> await identifier0.identifier1
or topic |> await identifier0.identifier1.identifier2
or so forth,
then the pipeline is a bare async function call.