should that work with all ASI context?

First off, it's not even an ASI problem. I just want to clarify that. You wish you had ASI in these scenarios, but you don't. 😃

It's sort of tough to nail down because not all of these are type errors off the bat. The other one that comes to mind is accessing a member off of an array which actually got parsed as an element access with a comma expression:

foo()
[1, 2, 3].forEach(x => {
  return x * x;
})

On the bright side, we already catch some of these: https://twitter.com/drosenwasser/status/939589182833410048

I also want to say that this improvement is definitely higher-priority. If a user weren't using TypeScript, then it's significantly less likely that they'd have run into this problem.

Thanks a bunch @Kingwl! 💯