Re:Concurrency Models: Go vs Erlang
by stonemetal on Wednesday March 27, 2013 @07:49PM
(#5452667)
It is closer to the Go end of the spectrum. It provides agents, they are an asynchronous message handler kind of similar to a goroutine or an Erlang process. When an agent gets an uncaught exception it caches it, then any subsequent interactions will immediately throw an exception, until the agent's errors are cleared.(http://clojure.org/agents) Which sounds kind of reasonable but I could see it causing problems as you start to see exceptions thrown by code that had no hand in creating the problem and may not know how to fix it.
[ Parent
| on HN ]
There are no comments on this comment yet.