Re: Potluck - thread safe event loop with await semantics

[Christopher Allan Webber]

Chris Vine writes:

> On Mon, 22 Feb 2016 12:53:10 -0500
> "Thompson, David" <address@hidden> wrote:
>> On Mon, Feb 22, 2016 at 12:40 PM, Chris Vine
>> <address@hidden> wrote:
>> 
>> > The other thing that may require further work is the
>> > documentation.  I am used to doxygen or gtk-doc, neither of which I
>> > imagine will parse guile scheme code, so I will have to look into
>> > what is available (I don't like info).
>> >
>> > I'll post the URL when I have put it up.  
>> 
>> Please consider unifying with Chris Webber's 8sync project, which
>> covers the same territory and has been approved as an official GNU
>> project.
>> 
>> https://notabug.org/cwebber/8sync
>
> 8sync has a nice design but the two cannot be unified because (i) 8sync
> does not try to be thread safe (it is strictly single-threaded), and
> (ii) it does not wrap an external event loop such as the glib/gtk+
> event loop.  In a number of ways it is considerably more sophisticated
> than my code, because it does not reveal the event loop at all, nor for
> that matter does it explicitly reveal its await/resume continuations.
> It is highly abstracted.
>
> They are just different things, which happen to both use delimited
> continuations in the same way.  In particular, I think it essential
> that an asynchronous event loop should have the ability for worker
> threads to post events to it.
>
> Chris

Thanks for the kind words.  I'm amazed that you got thread safe
asynchronous code working in Guile in this way!  Admittedly I don't
understand how you've done it yet... hopefully I can look soon...

Maybe there is some way for our stuff to work together, I'm not sure.
I'd have to look further.  You're right that 8sync is more abstracted.

Regardless, I'm glad to see various approaches being explored in
Guile-land right now.  Hats off to your neat work!