Comments for On Clojure

Comment on A monad tutorial for Clojure programmers (part 1) by Clojure Monad Resources

Clojure Monad Resources — Thu, 09 May 2013 14:29:18 +0000

[…] 1.A Monad Tutorial For Clojure Programmers Part1 […]

Comment on Reusable method implementations for deftypes by khinsen

khinsen — Tue, 26 Feb 2013 17:36:16 +0000

I know, and I agree. But it seems the only way to disable emoticon conversion is through a global setting of the blog. Since I don’t own this blog, I can’t do that.

Comment on Reusable method implementations for deftypes by billsmithaustin

billsmithaustin — Tue, 26 Feb 2013 17:15:26 +0000

Thank you for the post. Your blogging platform converts open bracket colon “o” ([:o) to an emoticon, which impedes reading some of your code snippets.

Comment on A monad tutorial for Clojure programmers (part 1) by Affordance and Concision | Digital Digressions by Stuart Sierra

Affordance and Concision | Digital Digressions by Stuart Sierra — Mon, 04 Feb 2013 13:29:00 +0000

[...] can implement the Maybe monad in Clojure, but there’s less motivation to do so without the support of a static type checker. You could [...]

Comment on A monad tutorial for Clojure programmers (part 1) by Erroneous behavior of m-lift in clojure.algo.monads?! No, it’s only me…again! | Japila :: verba docent, exempla trahunt

Wed, 12 Dec 2012 23:11:54 +0000

[...] even reported an issue to Konrad Hinsen (the author of the library), but when I read the article A Monad Tutorial For Clojure Programmers (Part 1) I knew I was [...]

Comment on A monad tutorial for Clojure programmers (part 3) by khinsen

khinsen — Thu, 06 Dec 2012 16:08:41 +0000

m-plus is indeed different because not every monad has one. The minimal requirement for a monad are m-bind and m-result. The optional add-on package consists of m-zero and m-plus. The reason for defining m-zero and m-plus as part of a monad is that they make sense only if there’s also m-bind and m-result.

There are indeed cases where different useful definitions of m-plus exist for identical m-bind/m-result. The way to handle this in algo.monads is to define different monads. One could try to factor out this aspect, but that would also complicate the monad library. I am not convinced that it would be worth the effort.

Comment on A monad tutorial for Clojure programmers (part 3) by Mark

Mark — Thu, 06 Dec 2012 15:17:56 +0000

m-bind, m-result, and m-zero all enable some important aspect of the domonad macro. Does m-plus play any role in domonad? If not, it really seems like the odd man out and it’s not really clear to me why you’d define it as part of the monad. Couldn’t there be more than one valid way to chain together multiple data sources, and if so, shouldn’t the chaining function really be defined for the task at hand, rather than as part of the monad itself?

Comment on A monad tutorial for Clojure programmers (part 3) by khinsen

khinsen — Thu, 06 Dec 2012 13:39:43 +0000

The classic use-case for m-plus is chaining together multiple data sources, e.g. in parsers (different branches of the grammar being explored) or in backtracking in logic programming (as in core.logic).

Comment on A monad tutorial for Clojure programmers (part 3) by Mark

Mark — Thu, 06 Dec 2012 05:43:39 +0000

I’d like to see an example of some interesting use of m-plus.

Comment on Managing namespaces by Namespaces in Clojure are confusing | Smash Company

Namespaces in Clojure are confusing | Smash Company — Mon, 10 Sep 2012 19:57:59 +0000

[...] So far I have enjoyed working with Clojure, but I still get confused by name spaces, for the reasons… One aspect of Clojure that I have not been quite happy with is namespace management. In a bigger project that consists of several namespaces, I usually end up having nearly identical :use and :require clauses in the initial ns form. These clauses set up the project-specific set of symbols that I want to work with. Individual namespaces sometimes add symbols for their specific needs, of course. What bothers me is that I have to repeat the :use and :require clauses, often with :exclude or nly options with many symbols, in every single namespace. And of course I often forget a copy when updating my symbol set. Therefore I decided to look at how namespaces work in more detail, and try to find a better way to manage symbols in namespaces. [...]