You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be even more applications to such an operator.
It may seems to be a lot like the pipeline operator, but the purpose of this issue is to think wider about an operator that could be used in a less constrained way.
What do you think?
The text was updated successfully, but these errors were encountered:
Pipeline operator general purpose is to obtain better readability from
chain3(chain2(chain1(value)))
tovalue |> chain1 |> chain2 |> chain3
.Currently, without pipeline operator, we can do something like:
From my understanding, pipe is about putting something into a temporary var and using this var later in the same expression.
Pipe is something about:
Why not think about an operator whose global purpose would be to set a var into a temp variable then reusing it later?
Note: i'm using
↑
for set,↓
for get and,
for then, but it may not be the best proposal.pipeline would be:
we can store variable at any time:
and why not imagine storing vars with identifiers:
It may be even more applications to such an operator.
It may seems to be a lot like the pipeline operator, but the purpose of this issue is to think wider about an operator that could be used in a less constrained way.
What do you think?
The text was updated successfully, but these errors were encountered: