<story><title>F# Pipeline Operator in JavaScript with Babel</title><url>http://codereform.com/blog/post/babel-fsharp-pipeline-operator/</url></story><parent_chain></parent_chain><comment><author>zackmorris</author><text>Somewhat related, but I wish that more languages provided a reserved convenience variable for accessing the result of the previous function call:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;3326826&amp;#x2F;language-history-origin-of-variable-it-in-read-eval-print-loop&amp;#x2F;3342195&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackoverflow.com&amp;#x2F;questions&amp;#x2F;3326826&amp;#x2F;language-history...&lt;/a&gt;&lt;p&gt;&lt;pre&gt;&lt;code&gt;  Python and Ruby: _
  Shell: $?
  HyperTalk: it (my first exposure to the concept, even though it was more of a convention)
  Some Lisps: *, **, ***, ...
&lt;/code&gt;&lt;/pre&gt;
If we had that, then we could write:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  func1();
  func2(_);
  func3(_);
  ...
&lt;/code&gt;&lt;/pre&gt;
Which reminds me of PostScript, which lets you examine and manipulate the program&amp;#x27;s stack directly (the top of the stack is the previous result):&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.ugrad.math.ubc.ca&amp;#x2F;Flat&amp;#x2F;intro.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.ugrad.math.ubc.ca&amp;#x2F;Flat&amp;#x2F;intro.html&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.ugrad.math.ubc.ca&amp;#x2F;Flat&amp;#x2F;stack.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.ugrad.math.ubc.ca&amp;#x2F;Flat&amp;#x2F;stack.html&lt;/a&gt;&lt;p&gt;If I were implementing it, I would make the previous result and stack contents read-only so that it&amp;#x27;s conceptually the same as the pipeline operator except that it allows inspecting the intermediate value.</text></comment>
<story><title>F# Pipeline Operator in JavaScript with Babel</title><url>http://codereform.com/blog/post/babel-fsharp-pipeline-operator/</url></story><parent_chain></parent_chain><comment><author>alharith</author><text>There&amp;#x27;s also ReasonML for those looking to scratch the itch sooner.&lt;p&gt;Also, don&amp;#x27;t be turned off by the sea of comments. Pick one, they are all great. but yes ML language enthusiasts can be a bit overenthusiastic, but I don&amp;#x27;t fault them for that. They are all anxious to spread the gospel of ML. The Reason community on discord is excellent, one of the best I have had the pleasure to be a part of.&lt;p&gt;I didn&amp;#x27;t go with straight OCaml with js_of_ocaml because I wanted a better representation of what I was doing in JS land. There is an excellent write-up about it here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.javierchavarri.com&amp;#x2F;js_of_ocaml-and-bucklescript&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.javierchavarri.com&amp;#x2F;js_of_ocaml-and-bucklescript&amp;#x2F;&lt;/a&gt;</text></comment>