<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Partial Application on F# for Fun and Profit</title>
    <link>https://fsharpforfunandprofit.com/categories/partial-application/</link>
    <description>Recent content in Partial Application on F# for Fun and Profit</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 09 Jul 2015 00:00:00 +0000</lastBuildDate><atom:link href="https://fsharpforfunandprofit.com/categories/partial-application/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Refactoring the Monadster</title>
      <link>https://fsharpforfunandprofit.com/posts/monadster-3/</link>
      <pubDate>Thu, 09 Jul 2015 00:00:00 +0000</pubDate>
      
      <guid>https://fsharpforfunandprofit.com/posts/monadster-3/</guid>
      <description>UPDATE: Slides and video from my talk on this topic
Warning! This post contains gruesome topics, strained analogies, discussion of monads
Welcome to the third installment in the gripping tale of Dr Frankenfunctor and the Monadster!
We saw in the first installment how Dr Frankenfunctor created life out of dead body parts using &amp;ldquo;Monadster part generators&amp;rdquo; (or &amp;ldquo;M&amp;quot;s for short), that would, on being supplied with some vital force, return a live body part.</description>
    </item>
    
    <item>
      <title>Completing the body of the Monadster</title>
      <link>https://fsharpforfunandprofit.com/posts/monadster-2/</link>
      <pubDate>Wed, 08 Jul 2015 00:00:00 +0000</pubDate>
      
      <guid>https://fsharpforfunandprofit.com/posts/monadster-2/</guid>
      <description>UPDATE: Slides and video from my talk on this topic
Warning! This post contains gruesome topics, strained analogies, discussion of monads
Welcome to the gripping tale of Dr Frankenfunctor and the Monadster!
We saw in the previous installment how Dr Frankenfunctor created life out of dead body parts using &amp;ldquo;Monadster part generators&amp;rdquo; (or &amp;ldquo;M&amp;quot;s for short), that would, on being supplied with some vital force, return a live body part.</description>
    </item>
    
    <item>
      <title>Dr Frankenfunctor and the Monadster</title>
      <link>https://fsharpforfunandprofit.com/posts/monadster/</link>
      <pubDate>Tue, 07 Jul 2015 00:00:00 +0000</pubDate>
      
      <guid>https://fsharpforfunandprofit.com/posts/monadster/</guid>
      <description>UPDATE: Slides and video from my talk on this topic
Warning! This post contains gruesome topics, strained analogies, discussion of monads
For generations, we have been captivated by the tragic story of Dr Frankenfunctor. The fascination with vital forces, the early experiments with electricity and galvanism, and finally the breakthrough culminating in the bringing to life of a collection of dead body parts &amp;ndash; the Monadster.
But then, as we all know, the creature escaped and the free Monadster rampaged through computer science conferences, bringing fear to the hearts of even the most seasoned programmers.</description>
    </item>
    
    <item>
      <title>Partial application</title>
      <link>https://fsharpforfunandprofit.com/posts/partial-application/</link>
      <pubDate>Sun, 06 May 2012 00:00:00 +0000</pubDate>
      
      <guid>https://fsharpforfunandprofit.com/posts/partial-application/</guid>
      <description>In the previous post on currying, we looked at breaking multiple parameter functions into smaller one parameter functions. It is the mathematically correct way of doing it, but that is not the only reason it is done &amp;ndash; it also leads to a very powerful technique called partial function application. This is a very widely used style in functional programming, and it is important to understand it.
The idea of partial application is that if you fix the first N parameters of the function, you get a function of the remaining parameters.</description>
    </item>
    
    <item>
      <title>Partial Application</title>
      <link>https://fsharpforfunandprofit.com/posts/convenience-partial-application/</link>
      <pubDate>Mon, 16 Apr 2012 00:00:00 +0000</pubDate>
      
      <guid>https://fsharpforfunandprofit.com/posts/convenience-partial-application/</guid>
      <description>A particularly convenient feature of F# is that complicated functions with many parameters can have some of the parameters fixed or &amp;ldquo;baked in&amp;rdquo; and yet leave other parameters open. In this post, we&amp;rsquo;ll take a quick look at how this might be used in practice.
Let&amp;rsquo;s start with a very simple example of how this works. We&amp;rsquo;ll start with a trivial function:
// define a adding function let add x y = x + y // normal use let z = add 1 2 But we can do something strange as well &amp;ndash; we can call the function with only one parameter!</description>
    </item>
    
  </channel>
</rss>
