On Saturday, June 29, 2013 1:32:26 AM UTC-4, Brandon Bloom wrote: > > > CSP proper is amenable to certain kinds of automated correctness > analysis. > > No work has been done on that front for core.async as yet. > > Although a far cry from Go's race > detector<http://blog.golang.org/race-detector>, > Go did ship with one feature that is helpful for preventing a certain class > of bugs: explicit restriction to a send-only or receive-only channel via > constraining conversion or assignment. See > http://golang.org/ref/spec#Channel_types > > Although Go utilizes the type system to accomplish this at compile time, > core.async could achieve the same effect at runtime. Essentially, there > could be two conversion functions for wrapping a channel in a read-only or > write-only proxy object. > > I'm not sure if this is actually useful, but I'm curious: Has this been > considered? >
Yes, that's why some of the args are called 'ports'. We will probably have read/write ports representing just one end of a channel. Rich -- -- 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.
