Go Routines are much like Chicken's SRFI-18 threads, except that they can multiplex over multiple *real* threads if one should block.
Go also enjoys a rather robust Channels system, which is sort of like Scheme's ports, only it's type-safe by design. Wiki actually has a nice and short break-down on this: https://en.wikipedia.org/wiki/Goroutine#Concurrency -Dan On Wed, Nov 27, 2013 at 1:22 PM, "Jörg F. Wittenberger" < joerg.wittenber...@softeyes.net> wrote: > Am 27.11.2013 20:32, schrieb Hugo Arregui: > >> On 27/11/13, m...@freeshell.de wrote: >> >>> On a sidenote: >>> >>> It seems that there is an analgon to go routines on Erlang, which can be >>> accessed the LFE (Lisp Flavoured Erlang). However, that would require to >>> learn the entire Erlang VM ecosystem. >>> >> A Lisp Flavoured Erlang, what nice!. >> >> > Having implemented a language inspired by Erlang in LISP (Scheme that is) > and in a byzantine fault tolerant way atop; I feel from skimming over the > discussion that I more or less have seen those related problems in > practice. However the code I wrote to cope with them is for sure not > conforming to any pre-defined API. > > Without making any promises (((and having already droped the page titled > "walkthough" from this go chan's docs, thus given that "go" is about as > great a search term as "scheme" makes pretty sure that I will not really be > able to find it back again))): could I you please send me pointers to what > is considered the canonical documentation of features and requirements a > go-channel has to solve? ((I have only so much screen-reading time left > per day because of my health. I'd rather just use it to "code ahead" > instead of digging through stuff from the net.)) However for the same > health issues I have a little too much spare time :-/ And as indicated: > chances are that all I have to do is adapt some already tested code to fit > the API as per spec. > > let's try > > /Jörg > > > > > _______________________________________________ > Chicken-users mailing list > Chicken-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/chicken-users >
_______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
