Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Spec: Specify Feature BP (Block Pipelines) #17

Closed
js-choi opened this issue Mar 21, 2018 · 2 comments
Closed

Spec: Specify Feature BP (Block Pipelines) #17

js-choi opened this issue Mar 21, 2018 · 2 comments
Assignees
Labels
spec About spec.html

Comments

@js-choi
Copy link
Collaborator

js-choi commented Mar 21, 2018

See #1.

@js-choi js-choi self-assigned this Mar 21, 2018
@js-choi
Copy link
Collaborator Author

js-choi commented Mar 23, 2018

See also tc39/proposal-do-expressions#24, tc39/proposal-do-expressions#21, and tc39/proposal-do-expressions#22. Definitely need to use the block interpretation, not the IIFE interpretation, which would prevent await; the original point of smart pipelines was to avoid unnecessary IIFEs. Might still be simplest to forbid break, continue, and return inside pipelines. Investigate whether an abrupt completion can be forwarded without much modification to other expression clauses.

@js-choi
Copy link
Collaborator Author

js-choi commented Mar 23, 2018

Also see also babel/babel#3780 (comment). The semantics of the spec probably should match the semantics of the Babel transformation. This means that #11 might block this, since how pipelines in general are most elegantly transformed using the statement-hoisting described in babel/babel#3780 (comment) might affect how it also works with block pipelines.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
spec About spec.html
Projects
None yet
Development

No branches or pull requests

1 participant