Found something I don't like about it. :-) https://github.com/halgari/clojure-conj-2013-core.async-examples/blob/master/src/clojure_conj_talk/core.clj#L470
as mentioned at https://github.com/halgari/clojure-conj-2013-core.async-examples/blob/master/src/clojure_conj_talk/core.clj#L470 creates an unbounded queue. Is there anyway around this, or does: * design specs of core.async, requiring all >! and <! to be in lexical scope of go block, essentially imply this? Thanks! On Tue, Jan 28, 2014 at 3:59 PM, john walker <john.lou.wal...@gmail.com> wrote: > No problem, I'm glad you also think it is cool :) > > > On Tuesday, January 28, 2014 6:54:22 PM UTC-5, t x wrote: >> >> Hi John, >> >> This is great. I really like "minimal examples" to hack on / play with. >> >> Thanks! >> >> On Tue, Jan 28, 2014 at 3:46 PM, john walker <john.lo...@gmail.com> wrote: >> > This doesn't answer your question, but you might find it interesting if >> > you >> > search for actors on it: >> > >> > >> > https://github.com/halgari/clojure-conj-2013-core.async-examples/blob/master/src/clojure_conj_talk/core.clj >> > >> > >> > On Tuesday, January 28, 2014 6:43:19 PM UTC-5, t x wrote: >> >> >> >> Hi, >> >> >> >> With apologies for a vague question: >> >> >> >> Is there a library built on top of core.async that tries to mimic >> >> erlang-like processes? >> >> >> >> The main features I'm looking for are: >> >> >> >> * each channel has a single go-thread attached to it >> >> >> >> * >! sends messages of the form >> >> {:tag :message >> >> :return-channel ;; input channel associated with the go-thread >> >> we're running in >> >> :message ... actual message } >> >> >> >> I find that this is basically what I'm already doing, but it's just >> >> a bit clunky at the moment. >> >> >> >> Thanks! >> > >> > -- >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Clojure" group. >> > To post to this group, send email to clo...@googlegroups.com >> > Note that posts from new members are moderated - please be patient with >> > your >> > first post. >> > To unsubscribe from this group, send email to >> > clojure+u...@googlegroups.com >> > For more options, visit this group at >> > http://groups.google.com/group/clojure?hl=en >> > --- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Clojure" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to clojure+u...@googlegroups.com. >> > For more options, visit https://groups.google.com/groups/opt_out. > > -- > -- > 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. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- -- 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. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
