<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Maybe Operator</title>
	<atom:link href="http://www.programmersparadox.com/2007/12/26/the-maybe-operator/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.programmersparadox.com/2007/12/26/the-maybe-operator/</link>
	<description>Long form thoughts from a Software Engineer</description>
	<lastBuildDate>Thu, 19 Jan 2012 13:42:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Mzyk</title>
		<link>http://www.programmersparadox.com/2007/12/26/the-maybe-operator/comment-page-1/#comment-10236</link>
		<dc:creator>Mark Mzyk</dc:creator>
		<pubDate>Thu, 04 Mar 2010 17:17:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2007/12/26/the-maybe-operator/#comment-10236</guid>
		<description>@Jimage

That&#039;s an interesting thought, the comparison to the brain.  I hadn&#039;t considered it, but it brings up the point that the maybe operator and maybe monad likely have a place in artificial intelligence programming.  

It&#039;s possible use around incomplete data is also interesting.  However, I don&#039;t know about situations where that is often the case, that a program has incomplete data.  Programs today are written so that they have complete data or they fail.  If with incomplete data today&#039;s programs generally fail, does that mean having a maybe operator would allow a different path through the code instead of issuing an exception or throwing an error?  A third path to deal with the uncertainty instead of just erroring out.

It&#039;s worth pondering.</description>
		<content:encoded><![CDATA[<p>@Jimage</p>
<p>That&#8217;s an interesting thought, the comparison to the brain.  I hadn&#8217;t considered it, but it brings up the point that the maybe operator and maybe monad likely have a place in artificial intelligence programming.  </p>
<p>It&#8217;s possible use around incomplete data is also interesting.  However, I don&#8217;t know about situations where that is often the case, that a program has incomplete data.  Programs today are written so that they have complete data or they fail.  If with incomplete data today&#8217;s programs generally fail, does that mean having a maybe operator would allow a different path through the code instead of issuing an exception or throwing an error?  A third path to deal with the uncertainty instead of just erroring out.</p>
<p>It&#8217;s worth pondering.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimage</title>
		<link>http://www.programmersparadox.com/2007/12/26/the-maybe-operator/comment-page-1/#comment-10231</link>
		<dc:creator>Jimage</dc:creator>
		<pubDate>Thu, 04 Mar 2010 05:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2007/12/26/the-maybe-operator/#comment-10231</guid>
		<description>This came up in discussion during several IRC conversations recently, and I dubbed it the &#039;may or may not&#039; operator. It has great comedic value, but surely there must be some practical applications. We spoke of a language in which assumptions play a major role. Someone observed that the brain relies heavily on assumptions, and it&#039;s about the most powerful computer that exists. Perhaps the maybe operator could play a valuable role in dealing with incomplete data, in a similar way that the brain fills in the gaps in our awareness. Also, it seems to have a certain quantum property about it... something about calculating unobserved data without collapsing it. Such reasoning becomes pseudo-science very quickly without more in-depth knowledge on the subject, but it&#039;s worth considering. Maybe.</description>
		<content:encoded><![CDATA[<p>This came up in discussion during several IRC conversations recently, and I dubbed it the &#8216;may or may not&#8217; operator. It has great comedic value, but surely there must be some practical applications. We spoke of a language in which assumptions play a major role. Someone observed that the brain relies heavily on assumptions, and it&#8217;s about the most powerful computer that exists. Perhaps the maybe operator could play a valuable role in dealing with incomplete data, in a similar way that the brain fills in the gaps in our awareness. Also, it seems to have a certain quantum property about it&#8230; something about calculating unobserved data without collapsing it. Such reasoning becomes pseudo-science very quickly without more in-depth knowledge on the subject, but it&#8217;s worth considering. Maybe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Maybe Monad (In Ruby) &#124; Programmer&#8217;s Paradox</title>
		<link>http://www.programmersparadox.com/2007/12/26/the-maybe-operator/comment-page-1/#comment-98</link>
		<dc:creator>The Maybe Monad (In Ruby) &#124; Programmer&#8217;s Paradox</dc:creator>
		<pubDate>Fri, 15 Feb 2008 14:27:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2007/12/26/the-maybe-operator/#comment-98</guid>
		<description>[...] the tail end of last year I wrote a piece in which I waxed about a possible maybe operator. I haven&#8217;t looked into implementing anything like it because my time is limited and I [...]</description>
		<content:encoded><![CDATA[<p>[...] the tail end of last year I wrote a piece in which I waxed about a possible maybe operator. I haven&#8217;t looked into implementing anything like it because my time is limited and I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Smith</title>
		<link>http://www.programmersparadox.com/2007/12/26/the-maybe-operator/comment-page-1/#comment-11</link>
		<dc:creator>Kevin Smith</dc:creator>
		<pubDate>Thu, 27 Dec 2007 11:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2007/12/26/the-maybe-operator/#comment-11</guid>
		<description>My gut tells me that implementing maybe has farther reaching implications than just ternary logic. A maybe operator seems to hint at things like promises and forced evaluation. I guess it&#039;s because maybe implies that the value could become &quot;fixed&quot; later depending on conditions and so, you might want to re-evaluate it later. Kinda like the magic eight ball&#039;s answer of &quot;Maybe, try again later&quot;.

Haskell has a Maybe monad which might be similar to what you&#039;re describing:

http://en.wikipedia.org/wiki/Monads_in_functional_programming</description>
		<content:encoded><![CDATA[<p>My gut tells me that implementing maybe has farther reaching implications than just ternary logic. A maybe operator seems to hint at things like promises and forced evaluation. I guess it&#8217;s because maybe implies that the value could become &#8220;fixed&#8221; later depending on conditions and so, you might want to re-evaluate it later. Kinda like the magic eight ball&#8217;s answer of &#8220;Maybe, try again later&#8221;.</p>
<p>Haskell has a Maybe monad which might be similar to what you&#8217;re describing:</p>
<p><a href="http://en.wikipedia.org/wiki/Monads_in_functional_programming" rel="nofollow">http://en.wikipedia.org/wiki/Monads_in_functional_programming</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

