<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Free Applicative Functors · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1403.0749/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1403.0749/feed.xml" rel="self" type="application/rss+xml" /><item><title>Free Applicative Functors — mentioned by mbrock</title><link>https://news.ycombinator.com/item?id=12605888</link><guid isPermaLink="false">urn:hackerpapers:mention:1403.0749:12605888</guid><pubDate>Thu, 29 Sep 2016 15:13:07 GMT</pubDate><description>&lt;p&gt;Yeah, the free monad structures involve lots of lambdas. It&amp;#x27;s not so much that information is &amp;quot;lost&amp;quot;, more that you cannot see beyond the next lambda abstraction. From a DSL perspective, it&amp;#x27;s like you can only inspect the program so far as to know the next statement in the &amp;quot;do&amp;quot; block. To see what the next statement will be, you need to actually evaluate the current one. Instead of free monads, if you want very analyzable structures, look at free applicative functors. &amp;quot;Applicative functors are a generalisation of monads. Both allow the expression of effectful computations into an otherwise…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1403.0749/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
