UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Open console
2. Run:
  var x = await something();
3. Be told that 'await' is a bad keyword here

What is the expected behavior?
await should 'just work', saving developers from having to use .then() or callbacks.

What went wrong?
I know we're often told that devtools runs in the global scope, bit I've heard from a few places now that it's actually enclosed, and uses a little magic to put/use variables inside the global when they're created / evaluated. If that's the case, being able to use `= await()` would be super useful for me as a web developer, who wants to check the behavior of some kind of async operation.

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: n/a
OS Version: 10.0
Flash Version: