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

Normative: To use await in a pipeline, do x |> await f #71

Merged
merged 1 commit into from
Dec 16, 2017
Merged

Conversation

littledan
Copy link
Member

Subsumes #66

@littledan
Copy link
Member Author

I discussed this issue with @tschneidereit and others at the November 2017 TC39, who underscored that it was really important to have a solution for await and pipeline built-in, rather than banning the intersection. The feeling I got from some committee members (sorry, I don't remember which ones) was that it was OK to have the difference in semantics between |> await f and |> (await f). So, as a start, I'll merge this option.

@littledan littledan merged commit 0982b0f into master Dec 16, 2017
@littledan littledan mentioned this pull request Dec 21, 2017
@js-choi js-choi deleted the await branch September 14, 2021 22:00
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant