aboutsummaryrefslogtreecommitdiff
path: root/src/content/chapter1_functions/lesson07_pipelines/en.html
diff options
context:
space:
mode:
Diffstat (limited to 'src/content/chapter1_functions/lesson07_pipelines/en.html')
-rw-r--r--src/content/chapter1_functions/lesson07_pipelines/en.html25
1 files changed, 25 insertions, 0 deletions
diff --git a/src/content/chapter1_functions/lesson07_pipelines/en.html b/src/content/chapter1_functions/lesson07_pipelines/en.html
new file mode 100644
index 0000000..783ade9
--- /dev/null
+++ b/src/content/chapter1_functions/lesson07_pipelines/en.html
@@ -0,0 +1,25 @@
+<p>
+ It's common to want to call a series of functions, passing the result of one
+ to the next. With the regular function call syntax this can be a little
+ difficult to read as you have to read the code from the inside out.
+</p>
+<p>
+ Gleam's pipe operator <code>|></code> helps with this problem by allowing you
+ to write code top-to-bottom.
+</p>
+<p>
+ The pipe operator takes the result of the expression on its left and passes it
+ as an argument to the function on its right.
+</p>
+<p>
+ It will first check to see if the left-hand value could be used as the first
+ argument to the call. For example, <code>a |> b(1, 2)</code> would become
+ <code>b(a, 1, 2)</code>. If not, it falls back to calling the result of the
+ right-hand side as a function, e.g., <code>b(1, 2)(a)</code>
+</p>
+<p>
+ Gleam code is typically written with the "subject" of the function as the
+ first argument, to make it easier to pipe. If you wish to pipe to a different
+ position then a function capture can be used to insert the argument to the
+ desired position.
+</p>