Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for await #52

Open
KathleenDollard opened this issue Jul 25, 2014 · 0 comments
Open

Support for await #52

KathleenDollard opened this issue Jul 25, 2014 · 0 comments

Comments

@KathleenDollard
Copy link
Owner

I don't support await yet because I can't figure out the semantics, and you actually have two visions in your head depending.

What's really happening is more or less this

// code
await stuff
{
// more code
}

but what it looks like is

// code
await stuff
// more code

The simplicity of the second version was core to the design of async. However, I also think it trips people up and that the first approach will make it much easier to do certain types of analysis.

I have three design ideas

  • nest statements following await, per first code above
  • have await be a random keyword like continue
  • provide two "modes", async simple, async expanded

I really, really hate the idea of modes. But I see such serious problems with both of the other options I'm leaning to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant