Re: Designing API for a Markov Model

named after the model you are using, for clarity > > On Sunday, September 14, 2014 3:28:10 AM UTC+1, RJ Nowling wrote: >> >> Hi all, >> >> I'm new to Clojure and implementing a Markov Model as part of a larger >> project. I'd like some advice on the API

Re: Designing API for a Markov Model

here something you need that other's don't currently > offer/emphasize; or is this more of a learning project? > * Are you planning on or interested in open sourcing your work? > > Best > > Chris > > > > On Sunday, September 14, 2014 8:18:30 AM UTC-7, RJ Nowl

Re: Designing API for a Markov Model

function, or whether the model itself could be a function. If the mechanics > of the process are somewhat generic, and the `markov-model` is just data, > then it's good as it is. But I'd make sure that progress-state isn't just > an empty wrapper. > > > Jony >

Designing API for a Markov Model

re idiomatic for Clojure? Are multiple return types an accepted practice in Clojure? Is there a third, better way? Thanks in advance! RJ -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@google

Re: Allow Data Structure to Be Called as Function

[s] >   (reify clojure.lang.IFn >     (invoke [this] (str "Hello, " s > > ((make-foo "RJ")) > "Hello, RJ" > > I have to admit, though, that I'm unclear on the relative merits of defrecord > vs. reify. Anyone want to comment? > &g

Allow Data Structure to Be Called as Function

ing a data structure in Clojure? Thanks, RJ -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post.

Enhanced Primitive Support Syntax

er wants a different set of behaviors for a block of code in that namespaces, they could wrap the code in a macro called something like enhanced-primitive-support or old-primitive-support: (enhanced-primitive-support (+ a b) ) I was wondering why an approach like this was not taken? Thanks, R

Re: review the clojure.string code

Also, according to Merriam-Webster, uppercase and lowercase don't have hyphens in them. RJ On May 30, 3:49 pm, Stuart Halloway wrote: > I have been working on a branch [1] and haven't updated the ticket yet [2]. > Given the number of diverse (and sometimes opposite!)