News for hackers. Stuff that matters.
Re:Clojure core.async and Go: A Code Comparison by simpleglider on Thursday July 04, 2013 @03:56PM (#5992202)
Small bug irrelevant to the main point of the article: The very last golang example has a leak. If the timeout does occur, main will exit after a timeout and the spawned go routine will hang on the channel push.

I think the easiest fix is to make the channel buffered. "make(chan string)" => "make(chan string, 1)" Not sure if there is a more idiomatic golang way to accomplish this.

Re:Clojure core.async and Go: A Code Comparison by kisielk on Thursday July 04, 2013 @04:37PM (#5992334)
Once main exits the program does as well, so all other goroutines will be terminated.
Re:Clojure core.async and Go: A Code Comparison by simpleglider on Thursday July 04, 2013 @06:44PM (#5992738)
True. Leaks don't matter for programs that exit immediately. I was pointing it out because it is often relevant when using the timeout pattern.