Comments (5)
Phase 1:
x |>await o.m(a)
would be invalid. F# pipeline uses x |> await
, which I've been calling "bare await".
from proposal-smart-pipelines.
Ah yeah, whoops, forgot about that. I’ll have to tweak those examples. Thanks!
from proposal-smart-pipelines.
@js-choi Does that materially impact our ability to make the "brace-style smart pipe" a superset of F# pipes?
from proposal-smart-pipelines.
It does not affect phase two’s backward compatibility with phase one (F# pipes); it still works. I made corrections in the original post.
It only, as you said elsewhere, raises the question of whether x|>await
is actually necessary versus x|>{await %}
. I would make the case that it might be a reasonable shortcut to introduce from the beginning in the phase-one proposal, due to the special non-function-composable nature of await
(and yield
). In fact I was going to file an issue on your repository suggesting supporting also x|>yield
, since they clearly form a unique pair.
from proposal-smart-pipelines.
yea hope the do
proposal will pass or anyway there is no problems with
1 |> ( console.log(#), #+1 ) |> foo
const through = a => b => (a(), b)
1 |> through(()=> {
//
})(#) |> foo
from proposal-smart-pipelines.
Related Issues (20)
- Explainer: Explain difference between `|>` expression and `with` statement
- Spec: Specify Feature NP (N-ary Pipelines) HOT 4
- Spec: Specify Feature BP (Block Pipelines) HOT 2
- Spec: Specify Feature TS (`try` statements)
- Readme/Spec: Drop Feature FS (`for` statements) HOT 3
- Spec, Feature PF: Specify async pipeline functions
- Feature PP (pipelines with implicit head) seems weakly motivated HOT 5
- Spec: PipelineStep must cover ConditionalExpression with supplemental production
- Spec: Cross-reference all augmented sections
- How would this interop with stateful closures? HOT 2
- Readme: Separate additional features, goals, nomenclature, term rewriting, and relations to other proposals and languages HOT 1
- Readme: Separate goals into new document HOT 1
- Spec: Remove redundant rules for chain productions
- Why was `#` chosen as the topic reference? HOT 8
- Explainer: Add example from real code using RxJS and/or Observables
- Feature: Pipeline transforms HOT 2
- Full bare style option HOT 1
- [doc bug]: 'do expression' reference links refer only to ./relations.md#do-expressions && doubled 'do expression'-block HOT 1
- Exaggeration under With No Pipelines HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from proposal-smart-pipelines.